#33192: It is not possible to use a custom lookup/transorm in a CheckConstraint
-------------------------------------+-------------------------------------
Reporter: Fabien MICHEL | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) | Resolution:
Severity: Normal | worksforme
Keywords: lookup, transform, | Triage Stage:
CheckContraint, migrate | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Fabien MICHEL):
In this case, won't I expose my migration to use code that could be
ananchronic if the code of the custom lookup changes after the migration
has been created ?
Is it not better to embed the custom lookup on the migration which insert
the constraint in database ?
--
Ticket URL: <https://code.djangoproject.com/ticket/33192#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 on the web visit
https://groups.google.com/d/msgid/django-updates/071.0d941d03c3902c835129c84a30e2b11a%40djangoproject.com.
