summaryrefslogtreecommitdiff
path: root/tests/backends/sqlite
diff options
context:
space:
mode:
authorSimon Charette <charette.s@gmail.com>2018-12-11 03:06:24 -0500
committerCarlton Gibson <carlton.gibson@noumenal.es>2018-12-17 10:44:05 +0100
commit894cb13779e6d092974c873bd2cf1452554d2e06 (patch)
treeafebfdae496f68695b36db17af90f0bbbe902f3d /tests/backends/sqlite
parent7289874adceec46b5367ec3157cdd10c711253a0 (diff)
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.
Diffstat (limited to 'tests/backends/sqlite')
-rw-r--r--tests/backends/sqlite/tests.py6
1 files changed, 3 insertions, 3 deletions
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):