#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
-------------------------------------+-------------------------------------
Changes (by Om Dahale):
* owner: nobody => Om Dahale
* status: new => assigned
Comment:
Hello, I would like to work on this issue.
As pointed out by Paolo, I can -
1. make the output_field required when it can generate errors
2. and ask to specify the required attributes like max_length on migration
creation phase.
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:3>
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/0107018ba845d9ee-13911e40-bd63-488f-9564-ccb0c341ca2c-000000%40eu-central-1.amazonses.com.
