#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => worksforme
Comment:
It works for me when you register a custom lookup as
[https://docs.djangoproject.com/en/stable/howto/custom-lookups/#a-lookup-
example documented]:
''"You will need to ensure that this registration happens before you try
to create any querysets using it. You could place the implementation in a
`models.py` file, or register the lookup in the `ready()` method of an
`AppConfig`"''
--
Ticket URL: <https://code.djangoproject.com/ticket/33192#comment:4>
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.9248e643a2748b5cdec541b2356937bf%40djangoproject.com.
