#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:14 Simon Charette]:
> For the second part of the problem, `CharField(None)`, I think that the
addition of a check is in order. Adding a
`GeneratedField._check_output_field` that simply delegates to
`self.output_field.check(**kwargs)` seems like the way to go to catch all
misuse of `output_field`.
Hello, Simon!
I raised a [https://github.com/django/django/pull/17458 PR] can you please
have a look and let me know if I am going in the right direction?
--
Ticket URL: <https://code.djangoproject.com/ticket/34944#comment:23>
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/0107018bb06f771d-1872a719-6736-4cc6-bf3c-5fd2181a4a91-000000%40eu-central-1.amazonses.com.
