#19173: "query" param for Model.objects.none() queryset has unexpected value.
-----------------------------------+--------------------------------------
Reporter: joshua.fialkoff@… | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.4
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 created another ticket for emptyqs removal - see #19184.
I am going to close this ticket. As Alex said qs.query isn't part of
public API, so we don't have to guarantee it works like in
`qs.filter(pk__in=[])`. If we want to fix this IMO the proper fix is to
just remove the emptyqs altogether which ensures qs.none() will work like
`qs.filter(pk__in=[])` works in every case - not just str(qs.query) case.
--
Ticket URL: <https://code.djangoproject.com/ticket/19173#comment:3>
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 https://groups.google.com/groups/opt_out.
