On 11/15/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote: > > So Alex *is* seeing broken behaviour here as it relates to > http://code.djangoproject.com/ticket/2993 where use of LazyDate was > broken in changeset 3960.
Sorry - that one is my fault; I meant to get around to fixing it last week, but I got hit with a dose of the flu, and then I got sent away on business. I should be back in action by this weekend. Unfortunately, the fix isn't as simple as reverting the check from 'isinstance' to 'is None', because SQLite requires that ONLY date formatted strings are used for the save. Forcing data to be a Datetime instance and then converting to string was the easiest approach I could think of (although obviously flawed); using the datetime validator on the string is another possibility. I'm open to any other suggestions. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
