#36350: Custom field's db_check() not taken into account when deciding whether
to
recreate constraint.
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: (none)
Type: Bug | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* cc: Lily Foote, Carlton Gibson (added)
Comment:
It looks like there isn't a simple fix here and this is not officially
supported
I have found a forum discussion around wanting to be able to define a
constraint for a custom field: https://forum.djangoproject.com/t
/dynamically-populate-constraints-in-field-contribute-to-class/22934/5
A number of folks seem to be in favor of the change (will add them in cc),
so I think we could have a "New Feature" ticket to add support for this
--
Ticket URL: <https://code.djangoproject.com/ticket/36350#comment:7>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019672776d49-cef41df2-e350-4611-9ece-c445b21a001c-000000%40eu-central-1.amazonses.com.
