#19881: get_next/previous_by_FOO doesn't work properly with multiple managers
----------------------------------------------+--------------------
     Reporter:  jtiai                         |      Owner:  nobody
         Type:  Uncategorized                 |     Status:  new
    Component:  Database layer (models, ORM)  |    Version:  1.4
     Severity:  Normal                        |   Keywords:
 Triage Stage:  Unreviewed                    |  Has patch:  0
Easy pickings:  0                             |      UI/UX:  0
----------------------------------------------+--------------------
 Model methods get_next_by_FOO() and get_previous_by_FOO() doesn't honor
 original manager used but uses always default manager (first manager
 declared on a model).

 This might potentially return incorrect data, for example in cases where
 softdelete is used. Default manager would return all objects but normally
 user uses manager that returns only non-deleted objects. In that case
 get_next|pervious_by_FOO would return incorrect data.

 Possible workaround would be using proxy models.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/19881>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to