#34944: Missing or misinferred attributes in output fields of generated fields
-------------------------------------+-------------------------------------
Reporter: Paolo Melchiorre | Owner: Om Dahale
Type: Bug | Status: assigned
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: field, database, | Triage Stage: Accepted
generated, output_field |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Lily Foote):
I'm curious if there are other expressions that could lead to an increased
column size or if it's just `Concat`. Maybe we could add something to
`Concat` (and other relevant expressions) that can express that column
size change?
If that's not feasible I would lean towards detecting the case where the
column size could be invalid and require `output_field` explicitly in
those cases. I'd be sad if `GeneratedField` always required an explicit
`output_field`.
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:11>
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/0107018baa37ada1-850118c3-d3f8-4541-8fb7-819d58ee9a41-000000%40eu-central-1.amazonses.com.
