#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 Mariusz Felisiak):
Replying to [comment:11 Andrey Ferriyan]:
> Any news on this?.
>
> Several codes broke due to the migration to the stable LTS version 4.2.
At least we have like temporary solution if it is possible.
I'm not sure what kind of news do you expect. This change was made in
Django 4.1 (which is already in extended support). Nobody started a
discussion as I [https://code.djangoproject.com/ticket/19580#comment:57
requested] 20 months ago, so there is nothing new here that could change a
previous decision. Also, please don't spread comments across multiple
tickets. If you have something to add, leave a comment in #19580.
--
Ticket URL: <https://code.djangoproject.com/ticket/33952#comment:12>
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/0107018b272ae035-42c7d857-b57e-443d-b14b-132e30b41ab7-000000%40eu-central-1.amazonses.com.
