diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index fe94aa006f..071e8b6449 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1131,8 +1131,6 @@ control the name of the aggregation value that is returned:: For an in-depth discussion of aggregation, see :ref:`the topic guide on Aggregation `. -.. _field-lookups: - ``exists()`` ~~~~~~~~~~~~ @@ -1147,6 +1145,8 @@ that it will be at some point, then using ``some_query_set.exists()`` will do more overall work (an additional query) than simply using ``bool(some_query_set)``. +.. _field-lookups: + Field lookups ------------- diff --git a/docs/releases/1.1-alpha-1.txt b/docs/releases/1.1-alpha-1.txt index 8cd695ef2d..664c354561 100644 --- a/docs/releases/1.1-alpha-1.txt +++ b/docs/releases/1.1-alpha-1.txt @@ -85,13 +85,13 @@ Other new features and changes introduced since Django 1.0 include: * The ``include()`` function in Django URLconf modules can now accept sequences of URL patterns (generated by ``patterns()``) in addition to module names. -* Instances of Django forms (see `the forms overview `_ now - have two additional methods, ``hidden_fields()`` and ``visible_fields()``, +* Instances of Django forms (see :ref:`the forms overview `) + now have two additional methods, ``hidden_fields()`` and ``visible_fields()``, which return the list of hidden -- i.e., ```` -- and visible fields on the form, respectively. -* The ``redirect_to`` generic view (see `the generic views documentation - `_) now accepts an additional keyword argument +* The ``redirect_to`` generic view (see :ref:`the generic views documentation + `) now accepts an additional keyword argument ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP temporary redirect (status code 302). @@ -99,7 +99,8 @@ Other new features and changes introduced since Django 1.0 include: * A new database lookup type -- ``week_day`` -- has been added for ``DateField`` and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday) and 7 (Saturday), and returns objects where the field value matches that day - of the week. See `the full list of lookup types `_ for details. + of the week. See :ref:`the full list of lookup types ` for + details. * The ``{% for %}`` tag in Django's template language now accepts an optional ``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop @@ -150,7 +151,7 @@ interested in helping out with Django's development, feel free to join the discussions there. Django's online documentation also includes pointers on how to contribute to -Django: +Django: * :ref:`How to contribute to Django ` diff --git a/docs/releases/1.1.txt b/docs/releases/1.1.txt index c69a4de2e4..61d76df7b6 100644 --- a/docs/releases/1.1.txt +++ b/docs/releases/1.1.txt @@ -392,13 +392,13 @@ Other new features and changes introduced since Django 1.0 include: * The ``include()`` function in Django URLconf modules can now accept sequences of URL patterns (generated by ``patterns()``) in addition to module names. -* Instances of Django forms (see `the forms overview `_ now - have two additional methods, ``hidden_fields()`` and ``visible_fields()``, +* Instances of Django forms (see :ref:`the forms overview `) + now have two additional methods, ``hidden_fields()`` and ``visible_fields()``, which return the list of hidden -- i.e., ```` -- and visible fields on the form, respectively. -* The ``redirect_to`` generic view (see `the generic views documentation - `_) now accepts an additional keyword argument +* The ``redirect_to`` generic view (see :ref:`the generic views documentation + `) now accepts an additional keyword argument ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP temporary redirect (status code 302). @@ -406,7 +406,8 @@ Other new features and changes introduced since Django 1.0 include: * A new database lookup type -- ``week_day`` -- has been added for ``DateField`` and ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday) and 7 (Saturday), and returns objects where the field value matches that day - of the week. See `the full list of lookup types `_ for details. + of the week. See :ref:`the full list of lookup types ` for + details. * The ``{% for %}`` tag in Django's template language now accepts an optional ``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop