#29868: Database constraint checks are not retained on sqlite
-------------------------------------+-------------------------------------
Reporter: Scott Stevens | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: check constraint | Triage Stage: Ready for
sqlite | 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:"630f3d8b466570cb13c3f998007e1d9d7b9a5f9b" 630f3d8b]:
{{{
#!CommitTicketReference repository=""
revision="630f3d8b466570cb13c3f998007e1d9d7b9a5f9b"
Refs #29868 -- Prevented name collisions between test constraints on
Oracle.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29868#comment:8>
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/067.0f7c3db4e3de8d31e5270d3cdcae5f9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
