#25467: Excluding an object with no ID excludes everything.
-------------------------------------+-------------------------------------
Reporter: skorokithakis | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
I'm not sure there is any ambiguity here. Clearly an unsaved instance
doesn't match any row in the database, so if it does anything besides
raise an exception, it should behave as "no match," just as the OP
desired.
That said, if "behave as no match" turns out to be infeasible to implement
cleanly, I'm not opposed to just raising an exception. I don't think this
is an important use case, there are alternative workarounds.
--
Ticket URL: <https://code.djangoproject.com/ticket/25467#comment:5>
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/071.05b16e4c87ea833b1093cfbe6864a8ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
