#34954: Improve `output_field` resolution in `GenerateField`
-------------------------------------+-------------------------------------
Reporter: Paolo | Owner: nobody
Melchiorre |
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: dev
layer (models, ORM) | Keywords: field, database,
Severity: Normal | generated, output_field
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
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 [https://code.djangoproject.com/ticket/34944#comment:17 Simon
Charette]
> FWIW I create [https://github.com/django/django/pull/17453 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34954>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018badfc6326-e9f13ac8-1abd-45ad-93ee-1ff9a8a71704-000000%40eu-central-1.amazonses.com.
