#30258: Failed to add CheckConstraint on IntegerRangeField
-------------------------------------+-------------------------------------
Reporter: Tilman Koschnick | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
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:"883d87074dd916224e2436ecc3dad8dd80e87c16" 883d870]:
{{{
#!CommitTicketReference repository=""
revision="883d87074dd916224e2436ecc3dad8dd80e87c16"
[2.2.x] Fixed #30258 -- Adjusted postgres schema value quoting of ranges.
Thanks Tilman Koschnick for the report and patch.
Backport of 386d89ab55e620440d30590a8a104fe6d5eef830 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30258#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.2b53f9a364c95afe280cde184f082616%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
