p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[1.5.x] Fixed #19881 -- Documented that get_next/previous_by_FOO uses default manager. 

Backport of ba610cb319 from master
This commit is contained in:
James Bennett 2013-06-20 01:36:13 -05:00 committed by Tim Graham
parent ee8996d8a6
commit 9b0604e514
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/ref/models/instances.txt
View File

@ -661,8 +661,11 @@ For every :class:`~django.db.models.DateField` and
returns the next and previous object with respect to the date field, raising returns the next and previous object with respect to the date field, raising
a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate. a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate.
Both methods accept optional keyword arguments, which should be in the format Both of these methods will perform their queries using the default
described in :ref:`Field lookups <field-lookups>`. manager for the model. If you need to emulate filtering used by a
custom manager, or want to perform one-off custom filtering, both
methods also accept optional keyword arguments, which should be in the
format described in :ref:`Field lookups <field-lookups>`.
Note that in the case of identical date values, these methods will use the Note that in the case of identical date values, these methods will use the
primary key as a tie-breaker. This guarantees that no records are skipped or primary key as a tie-breaker. This guarantees that no records are skipped or