#19881: Document that get_next/previous_by_FOO uses default manager
--------------------------------------+------------------------------------
Reporter: jtiai | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.4
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
I don't think this is worth adding another keyword argument to these
functions. It's a bit of a smell to have "special" kwarg names for a
function that otherwise interprets all its kwargs as field filters. And
the new argument doesn't fully solve the problem as phrased in the ticket;
you'd still get the "wrong" filtering initially and have to go digging to
figure out a) what's happening and b) the name of the keyword arg you need
to use to work around it. If people are going to need to do that digging
anyway, I think the manual-filtering and proxy-model workarounds are good
enough, and both work today.
So I still think this should just be documented, with mention of both
filtering manually and using a proxy model.
--
Ticket URL: <https://code.djangoproject.com/ticket/19881#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
