Skip to content
Browse files

Fixed #9255: Removed now-obsolete warning about the old semantics of …

…__exact=None vs. __isnull=True

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 8e608c2 commit 73c0db8e421bcb1621a5be59e5cf0fd0421e12d9 @ubernostrum ubernostrum committed
Showing with 0 additions and 8 deletions.
  1. +0 −8 docs/ref/models/querysets.txt
8 docs/ref/models/querysets.txt
@@ -1182,14 +1182,6 @@ SQL equivalent::
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.

0 comments on commit 73c0db8

Please sign in to comment.
Something went wrong with that request. Please try again.