On 6/12/05, Anduin Withers <[EMAIL PROTECTED]> wrote: > It is a DST thing. It is trying to make the best of a bad situation. There > was no 2:40 on April 3, 2005. > > The first time through the date is fetched from the DB and made a DateTime > from a string. When you make the delete a time_t is sent to the backend and > converted (as a time_t this time, not by parsing it as a string). The time > in question doesn't exist, so a time that does exist is returned. > > This would only apply to recordings starting/ending in time that doesn't > exist.
Okay, makes sense. At least for those of us who live in areas that change the clock :) But then the bug is that a non-existent time was stored in the DB, no? -- aaron _______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
