Opened 13 months ago

Last modified 12 months ago

#34954 assigned Cleanup/optimization

Improve `output_field` resolution of `Concat`

Reported by: Paolo Melchiorre Owned by: Simon Charette
Component: Database layer (models, ORM) Version: dev
Severity: Normal Keywords: field, database, generated, output_field
Cc: Simon Charette, Lily Foote Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Simon proposed in this comment to release blocker issue #34944 , to open a new improvement issue for a version of Django after 5.0

Replying to Simon Charette

FWIW I create a draft MR to demonstrate how Concat resolving could be enhanced but I still think that we should not included it in 5.0. Might be worth a follow up cleanup/optimization ticket though.

Change History (2)

comment:1 by Mariusz Felisiak, 13 months ago

Cc: Simon Charette Lily Foote added
Triage Stage: UnreviewedAccepted

comment:2 by Simon Charette, 12 months ago

Owner: changed from nobody to Simon Charette
Status: newassigned
Summary: Improve `output_field` resolution in `GenerateField`Improve `output_field` resolution of `Concat`

Renaming the ticket as it cannot be done generically for GeneratedField. Each expression must be adapted to do a better job at dealing with mixed input and my comment was solely for concat which is straight forward to resolve.

Note: See TracTickets for help on using tickets.
Back to Top