diff options
| author | James Bennett <ubernostrum@gmail.com> | 2008-09-30 22:29:58 +0000 |
|---|---|---|
| committer | James Bennett <ubernostrum@gmail.com> | 2008-09-30 22:29:58 +0000 |
| commit | 73c0db8e421bcb1621a5be59e5cf0fd0421e12d9 (patch) | |
| tree | 87e5d69d9b1824608420b5b9db66d9b054725e92 /docs/ref/models | |
| parent | 8e608c2155a4a466f1a4bf87df05c4e4ebd90c1c (diff) | |
Fixed #9255: Removed now-obsolete warning about the old semantics of __exact=None vs. __isnull=True
git-svn-id: http://code.djangoproject.com/svn/django/trunk@9105 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref/models')
| -rw-r--r-- | docs/ref/models/querysets.txt | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 9ffb3c34f9..4a41349fd7 100644 --- a/docs/ref/models/querysets.txt +++ b/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. - search ~~~~~~ |