#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: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [ticket:36350 Baptiste Mispelon]:
> I'm not sure if `Field.db_check()` can be considered public API (it's
not documented), but I have a fix which is fairly simple (PR incoming) so
I hope you'll consider it.
Unfortunately, the default implementation of `db_check()` already
incorporates the column name in generated SQL, so using it will
reintroduced issue fixed by 9953c804a9375956a542da94665662d306dff48d.
--
Ticket URL: <https://code.djangoproject.com/ticket/36350#comment:5>
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/01070196688b971d-e73ab631-1f3b-47c7-b9b7-491c0528ee83-000000%40eu-central-1.amazonses.com.
