Author: lukeplant
Date: 2011-10-08 11:07:30 -0700 (Sat, 08 Oct 2011)
New Revision: 16945
Modified:
django/trunk/docs/ref/models/querysets.txt
Log:
Fixed some ReST errors in docs.
Modified: django/trunk/docs/ref/models/querysets.txt
===================================================================
--- django/trunk/docs/ref/models/querysets.txt 2011-10-08 13:50:29 UTC (rev
16944)
+++ django/trunk/docs/ref/models/querysets.txt 2011-10-08 18:07:30 UTC (rev
16945)
@@ -605,6 +605,7 @@
class City(models.Model):
# ...
+ pass
class Person(models.Model):
# ...
@@ -679,7 +680,7 @@
.. versionchanged:: 1.2
You can also refer to the reverse direction of a
-:class:`~django.db.models.OneToOneField`` in the list of fields passed to
+:class:`~django.db.models.OneToOneField` in the list of fields passed to
``select_related`` — that is, you can traverse a
:class:`~django.db.models.OneToOneField` back to the object on which the field
is defined. Instead of specifying the field name, use the :attr:`related_name
@@ -760,7 +761,7 @@
>>> pizzas = Pizza.objects.prefetch_related('toppings')
>>> [list(pizza.toppings.filter(spicy=True)) for pizza in pizzas]
-...then the fact that `pizza.toppings.all()` has been prefetched will not help
+...then the fact that ``pizza.toppings.all()`` has been prefetched will not
help
you - in fact it hurts performance, since you have done a database query that
you haven't used. So use this feature with caution!
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
