#22817: Missing custom methods on EmptyQuerySet
-------------------------------+--------------------------------------
Reporter: benjaoming | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.6
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by benjaoming):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
See also #19184 for the reasoning behind removing EmptyQuerySet.
Can you perhaps imagine something like this:
{{{
class QuerySet():
def __init__(self, is_empty=False):
self.is_empty = is_empty
# Same for exclude and other core functions...
def filter(self, **kwargs):
# Do not hit database when empty!
if self.is_empty:
return self
def none(self):
self.is_empty = True
return self
class Manager():
...
def get_empty_queryset(self):
return QuerySet(empty=True)
...
def none(self):
return QuerySet(empty=True)
# Backwards compatible...
class EmptyQuerySet():
def __init__(self, ...):
return QuerySet(empty=True)
}}}
That way, EmptyQuerySet can continue to exist and still be deprecated?
--
Ticket URL: <https://code.djangoproject.com/ticket/22817#comment:1>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.56b75739d911c570325930b13d41a0dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
