From 9b0604e5149e20fc98f07256af60eac87421a346 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Thu, 20 Jun 2013 01:36:13 -0500 Subject: [PATCH] [1.5.x] Fixed #19881 -- Documented that get_next/previous_by_FOO uses default manager. Backport of ba610cb319 from master --- docs/ref/models/instances.txt | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index 92071b8d3f3..3d4c1fcadda 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -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 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 `. +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 `. 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