#30258: Failed to add CheckConstraint on IntegerRangeField
-------------------------------------+-------------------------------------
Reporter: Tilman Koschnick | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: 2.2
(models, ORM) |
Severity: Release blocker | Resolution:
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 Simon Charette):
I gave the `create_sql`/`constraint_sql` methods returning `(sql, params)`
[https://github.com/charettes/django/pull/new/constraint-index-sql a go]
but it would require a non-trivial refactor of `deferred_sql`. I still
think it would be worthy to make and might even be required in the future
to handle the quoting on backends that don't expose low level quoting
facilities like `psycopg2` does. The number of reports regarding similar
crashes now that `CheckConstraint`, `UniqueConstraint(condition)`, and
`Index(condition)` are out there will be good indicator of whether or not
this is required.
--
Ticket URL: <https://code.djangoproject.com/ticket/30258#comment:3>
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.ffa4b34510a64d39af4a1723f46a9a06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
