#30023: SQLite schema editor can cause table corruption if used within a
transaction since Django 2.0
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
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
-------------------------------------+-------------------------------------
Changes (by Simon Charette <charette.s@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"315357ad25a6590e7f4564ec2e56a22132b09001" 315357ad]:
{{{
#!CommitTicketReference repository=""
revision="315357ad25a6590e7f4564ec2e56a22132b09001"
Fixed #30023 -- Prevented SQLite schema alterations while foreign key
checks are enabled.
Prior to this change foreign key constraint references could be left
pointing
at tables dropped during operations simulating unsupported table
alterations
because of an unexpected failure to disable foreign key constraint checks.
SQLite3 does not allow disabling such checks while in a transaction so
they
must be disabled beforehand.
Thanks ezaquarii for the report and Carlton and Tim for the review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30023#comment:6>
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.e0853d5debc5daa3dd34bbd2bcadf498%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
