#33996: Inconsistent behavior of CheckConstraints validation on None values.
-------------------------------------+-------------------------------------
Reporter: James Beith | Owner: David
| Sanders
Type: Bug | Status: closed
Component: Database layer | Version: 4.1
(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
-------------------------------------+-------------------------------------
Comment (by GitHub <noreply@…>):
In [changeset:"36a000858b5eee13b039aaad490c33b037a1dc05" 36a00085]:
{{{#!CommitTicketReference repository=""
revision="36a000858b5eee13b039aaad490c33b037a1dc05"
Refs #33996 -- Updated CheckConstraint validation on NULL values on Oracle
23c+.
Oracle 23c supports comparing boolean expressions.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33996#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018e41e4d507-4da1faf6-93f6-40a2-a052-e534c50d8548-000000%40eu-central-1.amazonses.com.
