#36122: Add sanity check against updating non-composite field with composite
expression
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 5.2
(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 Sarah Boyce <42296566+sarahboyce@…>):
In [changeset:"d4d2e09f19e5d764b8b4df34f048f8babf670e8e" d4d2e09]:
{{{#!CommitTicketReference repository=""
revision="d4d2e09f19e5d764b8b4df34f048f8babf670e8e"
[5.2.x] Fixed #36122 -- Raised FieldError when updating with composite
reference value.
Thanks Jacob Walls for the report and test.
Backport of efec74b90868c2e611f863bf4301d92ce08067e8 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36122#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070194acdac8f5-256cef81-ecd6-41d7-b481-3c9ab4516a6f-000000%40eu-central-1.amazonses.com.
