#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 Mariusz Felisiak):
> Should we consider making this a deprecation warning for now, and adding
the strict validation in Django 5.x instead? (Admittedly, this isn't the
sort of thing you can write a startup check for, so it may be that a
deprecation warning would only help for apps that have good test coverage
anyhow.)
IMO deprecation is unnecessary, we raise an exception so it's not
something can be easily missed. Also, this is undocumented behavior and as
far as I'm aware it should be quite rare. If you think deprecation is
necessary, please first start a discussion on the DevelopersMailingList,
where you'll reach a wider audience and see what other think.
--
Ticket URL: <https://code.djangoproject.com/ticket/19580#comment:57>
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/066.a0bb5bf40534a981e6838e26236107fe%40djangoproject.com.
