#33952: Too aggressive pk control in create_reverse_many_to_one_manager
-------------------------------------+-------------------------------------
Reporter: Claude Paroz | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Alex Matos):
I already made a [https://code.djangoproject.com/ticket/19580#comment:58
comment] on #19580, but since this ticket is related, I'm gonna comment
here as well. I believe the changes on these two tickets should be fully
reverted. I'm upgrading a large Django codebase from version 3.2 to 4.2
and a lot of code broke due to these changes, where code that was once
returning an empty queryset, now raises a `ValueError`. In the name of
Django's stability, I think changing user code behavior without a
deprecation warning should be avoided at all costs.
--
Ticket URL: <https://code.djangoproject.com/ticket/33952#comment:10>
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/0107018b14f0d419-5b2411eb-1a22-454a-bd8d-806602a0db9c-000000%40eu-central-1.amazonses.com.
