Commit 73c0db8e authored by James Bennett's avatar James Bennett
Browse files

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
parent 8e608c21
Loading
Loading
Loading
Loading
+0 −8
Original line number Diff line number Diff line
@@ -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
~~~~~~