mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-06 10:49:17 +00:00
Code Issues 32 Releases Wiki Activity

queryset-refactor: Added a bunch of "new in development version" markers for

Browse Source 
recent additions.


git-svn-id: http://code.djangoproject.com/svn/django/branches/queryset-refactor@6520 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Malcolm Tredinnick 2007-10-15 03:58:20 +00:00
parent 44d51dae68
commit 3429fc0ff2
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/db-api.txt
View File

@ -533,6 +533,11 @@ primary key if there is no ``Meta.ordering`` specified. For example::
...since the ``Blog`` model has no default ordering specified. ...since the ``Blog`` model has no default ordering specified.
**New in Django development version:** The syntax for ordering across related
models has changed. See the `Django 0.96 documentation`_ for the old behaviour.
.. _Django 0.96 documentation: http://www.djangoproject.com/documentation/0.96/model-api/#floatfield
There's no way to specify whether ordering should be case sensitive. With There's no way to specify whether ordering should be case sensitive. With
respect to case-sensitivity, Django will order results however your database respect to case-sensitivity, Django will order results however your database
backend normally orders them. backend normally orders them.
@ -607,6 +612,9 @@ A couple of subtleties that are worth mentioning:
>>> Entry.objects.values('blog_id') >>> Entry.objects.values('blog_id')
[{'blog_id': 1}, ...] [{'blog_id': 1}, ...]
**New in Django development version:** Previously, it was not possible to pass
``blog_id`` to ``values()`` in the above example, only ``blog``.
A ``ValuesQuerySet`` is useful when you know you're only going to need values A ``ValuesQuerySet`` is useful when you know you're only going to need values
from a small number of the available fields and you won't need the from a small number of the available fields and you won't need the
functionality of a model instance object. It's more efficient to select only functionality of a model instance object. It's more efficient to select only
@ -1563,9 +1571,9 @@ This is equivalent to the following SQL ``WHERE`` clause::
You can compose statements of arbitrary complexity by combining ``Q`` objects You can compose statements of arbitrary complexity by combining ``Q`` objects
with the ``&`` and ``|`` operators. You can also use parenthetical grouping. with the ``&`` and ``|`` operators. You can also use parenthetical grouping.
``Q`` objects can also be negated using the ``~`` operator, allowing for **New in Django development version:** ``Q`` objects can also be negated using
combined lookups that combine both a normal query and a negated (``NOT``) the ``~`` operator, allowing for combined lookups that combine both a normal
query:: query and a negated (``NOT``) query::
Q(question__startswith='Who') | ~Q(pub_date__year=2005) Q(question__startswith='Who') | ~Q(pub_date__year=2005)