#29868: Database Check Constraints Not Retained (Only Last Is Stored)
-------------------------------------+-------------------------------------
Reporter: Scott Stevens | Owner: Simon
| Charette
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: check constraint | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => assigned
* owner: nobody => Simon Charette
* stage: Unreviewed => Accepted
Comment:
Thank you for your extra details. I confirmed the issue only affects
SQLite and is due to how we have to remake the table on this backend.
Currently working on a patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/29868#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.a5917ea88b8d4f76ec0ac7fff56b7e01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
