#30408: CheckConstraint with lookup using LIKE & % crash on Oracle and
PostgreSQL.
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 2.2
(models, ORM) |
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a8b3f96f6acfa082f99166e0a1cfb4b0fbc0eace" a8b3f96f]:
{{{
#!CommitTicketReference repository=""
revision="a8b3f96f6acfa082f99166e0a1cfb4b0fbc0eace"
Fixed #30408 -- Fixed crash when adding check constraints with LIKE
operator on Oracle and PostgreSQL.
The LIKE operator wildcard generated for contains, startswith, endswith
and
their case-insensitive variant lookups was conflicting with parameter
interpolation on CREATE constraint statement execution.
Ideally we'd delegate parameters interpolation in DDL statements on
backends
that support it but that would require backward incompatible changes to
the
Index and Constraint SQL generating methods.
Thanks David Sanders for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30408#comment:5>
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/066.965aad7bb6faa846e8d1250f3e888cce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
