#23264: db_constraint=False not enforced on migrations
---------------------------------+------------------------------------
Reporter: jmacul2 | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-rc-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by bmispelon):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Hi,
Indeed, the constraint seems to be created regardless of the
`db_constraint=False`.
Note that the same bux exists for `ManyToManyField.db_constraint`.
I'll bump the ticket to the `release blocker` status too.
Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/23264#comment:2>
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/065.de17d312890a74caacc04d41b3b826d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
