innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #12205 -- Corrected malformed reference links in the 1.1 and 1.1-alpha release notes, and corrected position of field lookup reference label. Thanks velmont and timo. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11988 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Gary Wilson Jr 2009-12-26 00:55:06 +00:00
parent 6154d58cb5
commit 39122c841f
3 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ref/models/querysets.txt
View File

@ -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 For an in-depth discussion of aggregation, see :ref:`the topic guide on
Aggregation <topics-db-aggregation>`. Aggregation <topics-db-aggregation>`.
.. _field-lookups:
``exists()`` ``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 more overall work (an additional query) than simply using
``bool(some_query_set)``. ``bool(some_query_set)``.
.. _field-lookups:
Field lookups Field lookups
------------- -------------

13
docs/releases/1.1-alpha-1.txt
View File

@ -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 * The ``include()`` function in Django URLconf modules can now accept sequences
of URL patterns (generated by ``patterns()``) in addition to module names. of URL patterns (generated by ``patterns()``) in addition to module names.
* Instances of Django forms (see `the forms overview <topics-forms-index>`_ now * Instances of Django forms (see :ref:`the forms overview <topics-forms-index>`)
have two additional methods, ``hidden_fields()`` and ``visible_fields()``, now have two additional methods, ``hidden_fields()`` and ``visible_fields()``,
which return the list of hidden -- i.e., ``<input type="hidden">`` -- and which return the list of hidden -- i.e., ``<input type="hidden">`` -- and
visible fields on the form, respectively. visible fields on the form, respectively.
* The ``redirect_to`` generic view (see `the generic views documentation * The ``redirect_to`` generic view (see :ref:`the generic views documentation
<ref-generic-views>`_) now accepts an additional keyword argument <ref-generic-views>`) now accepts an additional keyword argument
``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP
permanent redirect (status code 301). If ``False``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP
temporary redirect (status code 302). 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`` * 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 ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday)
and 7 (Saturday), and returns objects where the field value matches that day and 7 (Saturday), and returns objects where the field value matches that day
of the week. See `the full list of lookup types <field-lookups>`_ for details. of the week. See :ref:`the full list of lookup types <field-lookups>` for
details.
* The ``{% for %}`` tag in Django's template language now accepts an optional * The ``{% for %}`` tag in Django's template language now accepts an optional
``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop ``{% 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. discussions there.
Django's online documentation also includes pointers on how to contribute to Django's online documentation also includes pointers on how to contribute to
Django: Django:
* :ref:`How to contribute to Django <internals-contributing>` * :ref:`How to contribute to Django <internals-contributing>`

11
docs/releases/1.1.txt
View File

@ -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 * The ``include()`` function in Django URLconf modules can now accept sequences
of URL patterns (generated by ``patterns()``) in addition to module names. of URL patterns (generated by ``patterns()``) in addition to module names.
* Instances of Django forms (see `the forms overview <topics-forms-index>`_ now * Instances of Django forms (see :ref:`the forms overview <topics-forms-index>`)
have two additional methods, ``hidden_fields()`` and ``visible_fields()``, now have two additional methods, ``hidden_fields()`` and ``visible_fields()``,
which return the list of hidden -- i.e., ``<input type="hidden">`` -- and which return the list of hidden -- i.e., ``<input type="hidden">`` -- and
visible fields on the form, respectively. visible fields on the form, respectively.
* The ``redirect_to`` generic view (see `the generic views documentation * The ``redirect_to`` generic view (see :ref:`the generic views documentation
<ref-generic-views>`_) now accepts an additional keyword argument <ref-generic-views>`) now accepts an additional keyword argument
``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP ``permanent``. If ``permanent`` is ``True``, the view will emit an HTTP
permanent redirect (status code 301). If ``False``, the view will emit an HTTP permanent redirect (status code 301). If ``False``, the view will emit an HTTP
temporary redirect (status code 302). 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`` * 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 ``DateTimeField``. This type of lookup accepts a number between 1 (Sunday)
and 7 (Saturday), and returns objects where the field value matches that day and 7 (Saturday), and returns objects where the field value matches that day
of the week. See `the full list of lookup types <field-lookups>`_ for details. of the week. See :ref:`the full list of lookup types <field-lookups>` for
details.
* The ``{% for %}`` tag in Django's template language now accepts an optional * The ``{% for %}`` tag in Django's template language now accepts an optional
``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop ``{% empty %}`` clause, to be displayed when ``{% for %}`` is asked to loop