#36173: Usage of Concat with an explicit `output_field` results in unstable
migrations changes
-------------------------------------+-------------------------------------
Reporter: erchenstein | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 5.1
Severity: Normal | Resolution: fixed
Keywords: migrations concat | 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 <felisiak.mariusz@…>):
In [changeset:"8b1e324ca4aa1ae0721f6f5dcfba8325a751ef3c" 8b1e324]:
{{{#!CommitTicketReference repository=""
revision="8b1e324ca4aa1ae0721f6f5dcfba8325a751ef3c"
[5.2.x] Fixed #36173 -- Stabilized identity of Concat with an explicit
output_field.
When Expression.__init__() overrides make use of *args, **kwargs
captures their argument values are respectively bound as a tuple and
dict instances. These composite values might themselves contain values
that require special identity treatments such as Concat(output_field)
as it's a Field instance.
Refs #30628 which introduced bound Field differentiation but lacked
argument captures handling.
Thanks erchenstein for the report.
Backport of df2c4952df6d93c575fb8a3c853dc9d4c2449f36 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36173#comment:6>
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/010701950a35fade-5035bd38-64ec-47ce-ac21-37d59e4d674d-000000%40eu-central-1.amazonses.com.
