#19580: Unify reverse foreign key and m2m unsaved model querying
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: raydeal
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alex Matos):
I work on a large Django codebase and while upgrading it from version 3.2
to 4.2 a lot of code broke due to this change, where code that was once
returning an empty queryset, now raises a `ValueError`. In my opinion,
this change should be fully reverted. The partial update from #33952 is
not enough. I'm pretty sure I'm not alone in this situation. One of
Django's core strengths has always been its stability and breaking user
code without even a deprecation warning should be avoided at all costs.
--
Ticket URL: <https://code.djangoproject.com/ticket/19580#comment:58>
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/0107018b14e3b3d5-ce829a34-058e-4598-ae11-9968622f88f8-000000%40eu-central-1.amazonses.com.
