#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: closed
Component: contrib.postgres | Version: 4.1
Severity: Release blocker | Resolution: fixed
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:"e215948f0d75f69b11b8daff7628fb1212c00c27" e215948f]:
{{{
#!CommitTicketReference repository=""
revision="e215948f0d75f69b11b8daff7628fb1212c00c27"
[4.1.x] Fixed #33905 -- Fixed CheckConstraint() validation on range
fields.
Bug in 667105877e6723c6985399803a364848891513cc.
Backport of e0ae1363ec2aa71945be26f869cafd4181ccbc95 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33905#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 on the web visit
https://groups.google.com/d/msgid/django-updates/010701828424f41a-65f57bea-dd08-40ea-af63-35e666a67182-000000%40eu-central-1.amazonses.com.
