Author: ubernostrum
Date: 2008-09-30 17:29:58 -0500 (Tue, 30 Sep 2008)
New Revision: 9105
Modified:
django/trunk/docs/ref/models/querysets.txt
Log:
Fixed #9255: Removed now-obsolete warning about the old semantics of
__exact=None vs. __isnull=True
Modified: django/trunk/docs/ref/models/querysets.txt
===================================================================
--- django/trunk/docs/ref/models/querysets.txt 2008-09-30 22:25:41 UTC (rev
9104)
+++ django/trunk/docs/ref/models/querysets.txt 2008-09-30 22:29:58 UTC (rev
9105)
@@ -1182,14 +1182,6 @@
SELECT ... WHERE pub_date IS NULL;
-.. admonition:: ``__isnull=True`` vs ``__exact=None``
-
- There is an important difference between ``__isnull=True`` and
- ``__exact=None``. ``__exact=None`` will *always* return an empty result
- set, because SQL requires that no value is equal to ``NULL``.
- ``__isnull`` determines if the field is currently holding the value
- of ``NULL`` without performing a comparison.
-
search
~~~~~~
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
