#33618: Wrong behavior on queryset update when multiple inheritance
-------------------------------------+-------------------------------------
Reporter: Sonicold | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: queryset update | Triage Stage: Ready for
mutiple inheritance | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
It would be Django 4.1.
> Is there a big risk for us to patch manually the 4.x ?
Assuming you have good tests you could fork, apply
0b31e024873681e187b574fe1c4afe5e48aeeecf to a branch from `stable/4.0.x`.
That's essentially how we'd backport ourselves, by cherrypicking the
commit to the release branch.
To maintain that you would need to update your fork and rebase after each
4.0 point-release, but that's certainly do-able.
You could then install via [https://pip.pypa.io/en/stable/topics/vcs-
support/ Pip's VCS support].
I can't judge the degree of ''risk'' per se, it depends on your team, and
whether time is allocated for any issues that may arise.
(Part of the reasoning behind the backport policy is that release branches
should be largely stable though.)
I hope that helps.
--
Ticket URL: <https://code.djangoproject.com/ticket/33618#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070180042790ac-b0b8051b-4f82-435f-bd94-590ae4fd982e-000000%40eu-central-1.amazonses.com.
