#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 Paolo Melchiorre):
Replying to [comment:16 David Sanders]:
> Thanks Simon. I think we all seem to be in consensus about explicit
output_field… Lily & I were chatting on Discord (Paolo I believe you're on
there too) about how it seems unavoidable. 👍
Given the different time zone, I have only now read Discord, but I repeat
that, as I suspected in the description of the issue, it is inevitable at
this point to request an explicit `output_field`.
> ... just be aware that someone else may need to "take over" if things
stall seeing as this is a release blocker ;)
Thanks for making that clear.
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:19>
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/0107018badee4599-ae26426a-3b97-43df-a832-224a52f8d475-000000%40eu-central-1.amazonses.com.
