#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 Om Dahale):
Replying to [comment:4 Paolo Melchiorre]:
>
> Since this issue is a release blocker I hope you have time to propose an
MR ASAP :)
>
Okay
>
> Precisely, the two points I proposed as a solution are the ones that can
be implemented faster than others.
>
> For the point above:
>
> 1. "when it can generate errors" it can be difficult in all the cases,
maybe you can start asking every time for `output_field`
> 2. "attributes like max_length" we need to add tests for all model field
types
Noted
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ba8f1c293-076c4a72-e184-4060-bde7-8fbcd44cd07a-000000%40eu-central-1.amazonses.com.
