#17271: QuerySet.none() doesn't work well with subclasses of QuerySet
-------------------------------------+-------------------------------------
Reporter: andreypopp | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: SVN
(models, ORM) | Resolution: duplicate
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by andreypopp):
Replying to [comment:8 Wojciech Banaś <fizista@…>]:
> Your comments were very useful. Have combined your ideas with me, and I
received a very short and working code ([[ticket:17270]], see attachment
''manager.3.py'').
>
> Do you think that this solution would be good now?
It still generates new class at runtime and performs method mangling which
can be quite expensive in terms of performance. As I've already said, I
suggest to merge `Manager` and `QuerySet` functionality into single class
or eliminate one of them from public API, probably `Manager` is the best
candidate for this.
--
Ticket URL: <https://code.djangoproject.com/ticket/17271#comment:10>
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.
