#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):
Thanks for your report and patch, I turned it into a
[https://github.com/django/django/pull/11086 PR].
Happy to give you attribution if you can provide an email alias.
On a different subject this patch unveiled what I believe is a design flaw
with `Index` and `Constraint`'s `create_sql` and `remove_sql` methods.
They should return a tuple of SQL and a parms instead of a ''baked'' SQL
string so we can let the backend deal with the escaping itself. I'll spin
up a different PR that does just that.
--
Ticket URL: <https://code.djangoproject.com/ticket/30258#comment:2>
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.5b8c2fff545bcfd5353a98beda17881d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
