#17270: methods of the manager on subqueries QuerySet objects
-------------------------------------+-------------------------------------
Reporter: Wojciech Banaś | Owner: fizista@…
<fizista@…> | Status: new
Type: New feature | Version:
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: queryset manager | Needs documentation: 1
Extends | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by carljm):
As a longer-term project, I think finding a way to unify `Manager` and
`QuerySet` could be a real improvement to the ORM API, if we can find a
way to do it that is both sane and backwards compatible. The technique
here, dynamically creating a new `QuerySet` subclass on every access and
adding manager methods to it, is (probably mostly) backwards compatible,
but I am not at all convinced that it is sane, or an acceptable
performance hit.
--
Ticket URL: <https://code.djangoproject.com/ticket/17270#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
