mirror of
https://github.com/django/django.git
synced 2025-08-04 19:08:28 +00:00
Fixed #14141: docs now use the :doc: construct for links between documents.
Thanks, Ramiro Morales. git-svn-id: http://code.djangoproject.com/svn/django/trunk@13608 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
a352154e42
commit
728effcfbd
181 changed files with 1222 additions and 1525 deletions
|
@ -1,5 +1,3 @@
|
|||
.. _topics-db-aggregation:
|
||||
|
||||
===========
|
||||
Aggregation
|
||||
===========
|
||||
|
@ -8,7 +6,7 @@ Aggregation
|
|||
|
||||
.. currentmodule:: django.db.models
|
||||
|
||||
The topic guide on :ref:`Django's database-abstraction API <topics-db-queries>`
|
||||
The topic guide on :doc:`Django's database-abstraction API </topics/db/queries>`
|
||||
described the way that you can use Django queries that create,
|
||||
retrieve, update and delete individual objects. However, sometimes you will
|
||||
need to retrieve values that are derived by summarizing or *aggregating* a
|
||||
|
@ -363,7 +361,7 @@ you also select in a ``values()`` call.
|
|||
for you. The main reason is consistency with ``distinct()`` and other
|
||||
places: Django **never** removes ordering constraints that you have
|
||||
specified (and we can't change those other methods' behavior, as that
|
||||
would violate our :ref:`misc-api-stability` policy).
|
||||
would violate our :doc:`/misc/api-stability` policy).
|
||||
|
||||
Aggregating annotations
|
||||
-----------------------
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue