From 7cf9d15cf80df4ed9a1179bc457ff2d03b5e5cb3 Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Fri, 7 Dec 2018 19:55:47 -0500 Subject: [2.1.x] 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. Backport of 315357ad25a6590e7f4564ec2e56a22132b09001 from master. --- docs/releases/2.1.5.txt | 3 +++ 1 file changed, 3 insertions(+) (limited to 'docs/releases/2.1.5.txt') diff --git a/docs/releases/2.1.5.txt b/docs/releases/2.1.5.txt index 9f1f3a4e8a..f5306192a4 100644 --- a/docs/releases/2.1.5.txt +++ b/docs/releases/2.1.5.txt @@ -15,3 +15,6 @@ Bugfixes * Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and rebuild your SQLite database if you applied a migration while using an older version of Django with SQLite 3.26 or later (:ticket:`29182`). + +* Prevented SQLite schema alterations while foreign key checks are enabled to + avoid the possibility of schema corruption (:ticket:`30023`). -- cgit v1.2.1