Ticket #13263: 13263_docs_patch.diff

docs/topics/db/queries.txt

@@ -419 +419 @@
 it as if there is an empty (all values are ``NULL``), but valid, object there.
 All this means is that no error will be raised. For example, in this filter::
 
-    Blog.objects.filter(entry__author__name='Lennon')
+    Blog.objects.filter(entry__authors__name='Lennon')
 
 (if there was a related ``Author`` model), if there was no ``author``
 associated with an entry, it would be treated as if there was also no ``name``
@@ -427 +427 @@
 Usually this is exactly what you want to have happen. The only case where it
 might be confusing is if you are using ``isnull``. Thus::
 
-    Blog.objects.filter(entry__author__name__isnull=True)
+    Blog.objects.filter(entry__authors__name__isnull=True)
 
 will return ``Blog`` objects that have an empty ``name`` on the ``author`` and
 also those which have an empty ``author`` on the ``entry``. If you don't want
 those latter objects, you could write::
 
-    Blog.objects.filter(entry__author__isnull=False,
-            entry__author__name__isnull=True)
+    Blog.objects.filter(entry__authors__isnull=False,
+            entry__authors__name__isnull=True)
 
 Spanning multi-valued relationships
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -532 +532 @@
 the entries where the author's name is the same as the blog name, we could
 issue the query:
 
-    >>> Entry.objects.filter(author__name=F('blog__name'))
+    >>> Entry.objects.filter(authors__name=F('blog__name'))
 
 The pk lookup shortcut
 ----------------------