Opened 12 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
Concatresolving 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 , 12 months ago
| Cc: | added |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 12 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
| Summary: | Improve `output_field` resolution in `GenerateField` → Improve `output_field` resolution of `Concat` |
Note:
See TracTickets
for help on using tickets.
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.