#36350: Custom field's db_check() not taken into account when deciding whether
to
recreate constraint.
-------------------------------------+-------------------------------------
Reporter: Baptiste Mispelon | Owner: (none)
Type: New feature | Status: assigned
Component: Database layer | Version: 5.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* stage: Unreviewed => Accepted
* type: Bug => New feature
Comment:
I agree this looks like a new feature. I'll accept on that basis. (Happy
if someone wants to reclassify.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36350#comment:8>
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/0107019680935a65-3ee3e247-f3f7-454f-b6c2-5a65ef789d14-000000%40eu-central-1.amazonses.com.
