Skip to content
Browse files

Fixed #19881 -- Documented that get_next/previous_by_FOO uses default…

… manager.
  • Loading branch information...
1 parent b53ed5a commit ba610cb319d8882a663effcaf0a4e53c04593f98 @ubernostrum ubernostrum committed with timgraham
Showing with 5 additions and 2 deletions.
  1. +5 −2 docs/ref/models/instances.txt
7 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

0 comments on commit ba610cb

Please sign in to comment.
Something went wrong with that request. Please try again.