This time value appears in my database:
(2005, 4, 3, 3, 47, 43, 6, 93, -1)

Try this:
import time
time.mktime((2005, 4, 3, 2, 47, 43, 6, 93, -1))
time.mktime((2005, 4, 3, 1, 47, 43, 6, 93, -1))
time.mktime((2005, 4, 3, 3, 47, 43, 6, 93, -1))

The first mktime call fails with an overflow error. The other two pass. That's because the hour between 2 and 3 AM did not exist this past night. This datetime made it into the database through some addition (it wasn't a timestamp).

col.py's DateTimeValidator (line 745 in 0.6.1) choked on this value. Anyone have thoughts on the best way to handle this? I could try to be stricter in my timezones, or the validator could keep an eye out for this, since this is specifically a problem where the daily savings time status is unknown (the -1 at the end).

Kevin