On Tue, Oct 20, 2009 at 9:09 PM, Михаил Лукин <mihail.lu...@googlemail.com> wrote: > For some reason, __exact and __isnull are described in documentation [1], > while =None is not. So which of them are historical?
As I said, __exact and __isnull are historical. The documentation you reference points out that __exact=X and =X are equivalent. The =X form was added after the __exact form when the internal mechanics for query were changed in such a way that made the implied __exact form possible. The equivalence of __isnull and __exact occurred just before the release of 1.0, which is noted in [1]. Previously, __isnull=True was mapped to "IS NULL", and __equals=None was mapped to '= NULL'. As of v1.0, both map to IS NULL. [1] http://docs.djangoproject.com/en/dev/ref/models/querysets/#exact 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
