#25467: Excluding an object with no ID excludes everything.
-------------------------------------+-------------------------------------
Reporter: Stavros | Owner: Jacob
Korokithakis | Walls
Type: Bug | Status: assigned
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* owner: Joakim Israelsson => Jacob Walls
* has_patch: 0 => 1
Comment:
If I have captured the original case in the
[https://github.com/django/django/pull/14927 linked PR] correctly, option
(b) -- just treat the unsaved object as IS NULL -- was implemented in
58da81a5a372a69f0bac801c412b57f3cce5f188 (#27985).
From https://code.djangoproject.com/ticket/27985#comment:14 I see Simon
suggesting this:
"I feel like preventing unsaved objects from being used in all related
filters in future versions of Django would be the best course of action
here."
I suggest closing this ticket, or else reframe with Simon's suggestion to
raise an exception.
--
Ticket URL: <https://code.djangoproject.com/ticket/25467#comment:11>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.99ae0402cb5b1d8dc1a08e53310be294%40djangoproject.com.
