#33905: Validation of check constraints against ranges involving PostgreSQL's
lower()/upper() functions produces invalid SQL.
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: David
| Sanders
Type: Bug | Status: assigned
Component: contrib.postgres | Version: 4.1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"e0ac72fe80a806421dcbbbac22e483b27d2ede7b" e0ac72fe]:
{{{
#!CommitTicketReference repository=""
revision="e0ac72fe80a806421dcbbbac22e483b27d2ede7b"
Refs #33905 -- Added test for CheckConstraint() validation with ArrayField
and __contains.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33905#comment:6>
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/0107018284246c48-a7d84c1b-7121-4082-98dc-116986ea9401-000000%40eu-central-1.amazonses.com.
