test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Added note to docs/db-api.txt about 'depth' being new in Django development version 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@4649 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2007-02-28 19:42:29 +00:00
parent 37c66a0999
commit a81a6e9abe
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/db-api.txt
View File

@ -596,7 +596,7 @@ related ``Person`` *and* the related ``City``::
Note that ``select_related()`` does not follow foreign keys that have Note that ``select_related()`` does not follow foreign keys that have
``null=True``. ``null=True``.
Usually, using ``select_related()`` can vastly improve performance since your Usually, using ``select_related()`` can vastly improve performance because your
app can avoid many database calls. However, in situations with deeply nested app can avoid many database calls. However, in situations with deeply nested
sets of relationships ``select_related()`` can sometimes end up following "too sets of relationships ``select_related()`` can sometimes end up following "too
many" relations, and can generate queries so large that they end up being slow. many" relations, and can generate queries so large that they end up being slow.
@ -609,6 +609,8 @@ follow::
p = b.author # Doesn't hit the database. p = b.author # Doesn't hit the database.
c = p.hometown # Requires a database call. c = p.hometown # Requires a database call.
The ``depth`` argument is new in the Django development version.
``extra(select=None, where=None, params=None, tables=None)`` ``extra(select=None, where=None, params=None, tables=None)``
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~