#17271: QuerySet.none() doesn't work well with subclasses of QuerySet
-------------------------------------+-------------------------------------
Reporter: andreypopp | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: SVN
(models, ORM) | Resolution:
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 Wojciech Banaś <fizista@…>):
Replying to [comment:5 andreypopp]:
> Replying to [comment:4 Wojciech Banaś <fizista@…>]:
> > I tested also a problem with the method of none () in my
solution([[ticket:17270]]), and this problem does NOT exist there.
> >
> > So I think the filters should be located just in manager and not in
the QuerySet.
>
> I like to define methods on `QuerySet` because it allows chain several
filters at once:
> {{{
> users = User.objects.have_permission("some
permission").is_staff().have_new_messages()
> }}}
> and so on...
The same you can get by using my patch, and filters are where they should,
in the manager.
See my examples in this ticket [[ticket:17270]]
--
Ticket URL: <https://code.djangoproject.com/ticket/17271#comment:6>
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.
