Changeset 6520
- Timestamp:
- 10/14/07 22:58:20 (9 months ago)
- Files:
-
- django/branches/queryset-refactor/docs/db-api.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/branches/queryset-refactor/docs/db-api.txt
r6518 r6520 533 533 534 534 ...since the ``Blog`` model has no default ordering specified. 535 536 **New in Django development version:** The syntax for ordering across related 537 models has changed. See the `Django 0.96 documentation`_ for the old behaviour. 538 539 .. _Django 0.96 documentation: http://www.djangoproject.com/documentation/0.96/model-api/#floatfield 535 540 536 541 There's no way to specify whether ordering should be case sensitive. With … … 608 613 [{'blog_id': 1}, ...] 609 614 615 **New in Django development version:** Previously, it was not possible to pass 616 ``blog_id`` to ``values()`` in the above example, only ``blog``. 617 610 618 A ``ValuesQuerySet`` is useful when you know you're only going to need values 611 619 from a small number of the available fields and you won't need the … … 1564 1572 with the ``&`` and ``|`` operators. You can also use parenthetical grouping. 1565 1573 1566 ``Q`` objects can also be negated using the ``~`` operator, allowing for 1567 combined lookups that combine both a normal query and a negated (``NOT``) 1568 query ::1574 **New in Django development version:** ``Q`` objects can also be negated using 1575 the ``~`` operator, allowing for combined lookups that combine both a normal 1576 query and a negated (``NOT``) query:: 1569 1577 1570 1578 Q(question__startswith='Who') | ~Q(pub_date__year=2005)
