#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
-------------------------------+--------------------------------------
Comment (by akaariai):
I'm probably missing some piece here - why doesn't using .none() work in
1.7? This should return a QuerySet that doesn't hit the database when
executed.
I don't see any big problems in allowing creation of EmptyQuerySet classes
for backward compatibility, but I'd like to get a good picture of what is
happening before doing that. (The example above doesn't work, first,
`__init__` can't return anything, second it would return direct QuerySet
without any custom methods which by my understanding isn't the wanted
behaviour)
--
Ticket URL: <https://code.djangoproject.com/ticket/22817#comment:2>
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.757e61beeab69639dc52983f706f926f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
