diff options
| author | James Bennett <james@b-list.org> | 2013-06-20 01:36:13 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-06-21 13:14:05 -0400 |
| commit | ba610cb319d8882a663effcaf0a4e53c04593f98 (patch) | |
| tree | 840c68a90a1657392825996a33e1e253db99be7a | |
| parent | b53ed5ac55d5881f129c4921199af355e2b13565 (diff) | |
Fixed #19881 -- Documented that get_next/previous_by_FOO uses default manager.
| -rw-r--r-- | docs/ref/models/instances.txt | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index cfc95db092..17c9aa9fb7 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -679,8 +679,11 @@ For every :class:`~django.db.models.DateField` and returns the next and previous object with respect to the date field, raising a :exc:`~django.core.exceptions.DoesNotExist` exception when appropriate. -Both methods accept optional keyword arguments, which should be in the format -described in :ref:`Field lookups <field-lookups>`. +Both of these methods will perform their queries using the default +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 primary key as a tie-breaker. This guarantees that no records are skipped or |