#20625: Custom Chainable QuerySets
-------------------------------------+-------------------------------------
Reporter: danols | Owner: danols
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) | Resolution:
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 loic84):
Added another commit which fixes pickling, I believe this POC is as good
as it can be, we now have to decide whether it's the approach we want to
pursue.
If we decide to go for it, we need to settle on the scope (do we try to
deprecate all legacy proxy methods or not) and I'll turn it into a proper
patch with tests and docs.
For the record, I did try having `Manager` inherit from `QuerySet`, it's
quite hard because of all the magic methods. I also believe it's
undesirable in term of API as there are plenty of `QuerySet` methods - the
private ones in particular - that we don't want on the manager.
--
Ticket URL: <https://code.djangoproject.com/ticket/20625#comment:14>
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f334409001cf874abf961b0cab4f7e32%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
