#17494: Query Methods
-------------------------------------+-------------------------------------
Reporter: zacharyvoase | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by dstufft):
django-model-utils used to dynamically generate Querysets to achieve this,
which broke pickling them. I don't however know how it was dynamically
generated.
In general I think the idea here is to prevent you from having to define
the same method twice which that solution has, you just specify it on the
QuerySet, then add it to the PassThroughManager. Same Outcome without the
__metaclass__ magic which personally find hard to understand with
something that gives the same end result.
--
Ticket URL: <https://code.djangoproject.com/ticket/17494#comment:4>
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.
