#30412: CheckConstraint with OR operator generates incorrect SQL on SQLite and
Oracle.
-------------------------------------+-------------------------------------
Reporter: Michael Spallino | Owner: Can
| Sarıgöl
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: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"58391b4d164ac83b8001a2ec70f3b1e4d39e4681" 58391b4]:
{{{
#!CommitTicketReference repository=""
revision="58391b4d164ac83b8001a2ec70f3b1e4d39e4681"
[2.2.x] Fixed #30412 -- Fixed crash when adding check constraints with
OR'ed condition on Oracle and SQLite.
Backport of 719b7466203181066d9537d2e3bec687dffc9f41 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30412#comment:9>
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/070.f8e15b6b3a61eb543a1c5c007369f0ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
