#20625: Custom Chainable QuerySets
-------------------------------------+-------------------------------------
Reporter: danols | Owner: loic84
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: QuerySet, | Needs documentation: 0
models.Manager, chainable | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by Loic Bistuer <loic.bistuer@…>):
In [changeset:"c9a53035d61588bc7c76eb38db74b774d64b5c1c"]:
{{{
#!CommitTicketReference repository=""
revision="c9a53035d61588bc7c76eb38db74b774d64b5c1c"
Generate GeoManager from GeoQuerySet. Refs #20625.
This cleanup lays the groundwork for #23533 and also addresses
the issue that GeoManager.get_queryset() failed to pass the
database router hints to the QuerySet constructor.
Thanks Anssi Kääriäinen for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20625#comment:38>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.e276174e7ccd9bb7ba269f1b5a9ffe96%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
