mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-07-24 13:44:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Refs #29182 -- Stopped relying on legacy alter table semantic on SQLite 3.26+.

Browse source 
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.
This commit is contained in:
Simon Charette 2018-12-11 03:06:24 -05:00 • committed by Carlton Gibson
parent 7289874adc
commit 894cb13779
3 changed files with 9 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
tests/backends/sqlite/tests.py
View file

@ -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):