I have recently come across a slight difference in the way that datetimefields are handled by mysql and sqlite. Locally, on my desktop I use sqlite for debugging, while the production server runs mysql. Running django-trunk. One of my models includes a datetimefield:
last_fetched = models.DateTimeField(null=True, blank=True) In some of my instances the field is still None, while others have a datetime set. When trying to filter on the instances where the datetime is earlier/lower than a given date or the datetime is still None I initially tried something along the lines of: queryset_something.exclude(last_fetched__gt=given_date) On sqlite this returned both the datetimes that where lower and the once not yet set. On mysql, however, it did not return the empty datetimes. I then tried to use Q-objects, like this: queryset_something.filter(Q(last_fetched__lt=given_date) | Q(last_fetched__isnull = True)) This worked, but I keep wondering if this is the best sollution and if this actually is an unwanted inconsistency of Django. Comments? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
