From 894cb13779e6d092974c873bd2cf1452554d2e06 Mon Sep 17 00:00:00 2001 From: Simon Charette Date: Tue, 11 Dec 2018 03:06:24 -0500 Subject: Refs #29182 -- Stopped relying on legacy alter table semantic on SQLite 3.26+. SQLite 3.26 changed the behavior of table and column renaming operations to repoint foreign key references even if foreign key checks are disabled. This makes the workarounds in place to simulate this behavior unnecessary on SQLite 3.26+. Refs #30033. --- tests/backends/sqlite/tests.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'tests/backends/sqlite') diff --git a/tests/backends/sqlite/tests.py b/tests/backends/sqlite/tests.py index 46122dc38b..c5b9569eac 100644 --- a/tests/backends/sqlite/tests.py +++ b/tests/backends/sqlite/tests.py @@ -121,8 +121,8 @@ class SchemaTests(TransactionTestCase): new_field.set_attributes_from_name('renamed') msg = ( "Renaming the 'backends_author'.'name' column while in a " - "transaction is not supported on SQLite because it would break " - "referential integrity. Try adding `atomic = False` to the " + "transaction is not supported on SQLite < 3.26 because it would " + "break referential integrity. Try adding `atomic = False` to the " "Migration class." ) with self.assertRaisesMessage(NotSupportedError, msg): @@ -136,7 +136,7 @@ class SchemaTests(TransactionTestCase): """ msg = ( "Renaming the 'backends_author' table while in a transaction is " - "not supported on SQLite because it would break referential " + "not supported on SQLite < 3.26 because it would break referential " "integrity. Try adding `atomic = False` to the Migration class." ) with self.assertRaisesMessage(NotSupportedError, msg): -- cgit v1.3