#33618: Wrong behavior on queryset update when multiple inheritance
-------------------------------------+-------------------------------------
Reporter: Sonicold | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset update | Triage Stage: Accepted
mutiple inheritance |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
> I'll let Mariusz and Carlton chime in here. This is a data loss issue so
[https://docs.djangoproject.com/en/4.0/internals/release-process/ it
should theoretically qualify] but the issue has been around forever and
only happens for uncommon model structures so I'd be wary of introducing a
regression via a minor version if this was backported and possibly cause a
different kind of data loss issue.
IMO, the risk of introducing another regression is too great. Moreover it
was reported after Django 2.2 EOL (April, 1st) so it wouldn't be
backported regardless of our decision.
--
Ticket URL: <https://code.djangoproject.com/ticket/33618#comment:7>
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/0107018002775180-d7b9bc8a-7c4a-41b0-927c-804d52bfabcf-000000%40eu-central-1.amazonses.com.
