From 73c0db8e421bcb1621a5be59e5cf0fd0421e12d9 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Tue, 30 Sep 2008 22:29:58 +0000 Subject: [PATCH] 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 --- docs/ref/models/querysets.txt | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index 9ffb3c34f95ef..4a41349fd742a 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 ~~~~~~