#21966: Incorrect usage of constraint_checks_disabled in tests
-------------------------------+--------------------------------------
Reporter: wlodek | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: master
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => needsinfo
Comment:
Indeed, `constraint_checks_disabled` and related APIs exist only because
MySQL is unable to defer constraints checks until transaction commit. See
#3615 for details.
I read your description a few times and I don't understand what your
proposal actually is. Maybe you could take this to the
DevelopersMailingList?
--
Ticket URL: <https://code.djangoproject.com/ticket/21966#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/064.b6536b4407eada3da874896ecd28a18c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
