我尝试将Django连接到Azure SQL,但在开始迁移命令时出现错误KeyError: deferrable。我找不到解决这个问题的办法。
我使用这个应用程序:
asgiref==3.2.10
Django==3.1
django-mssql-backend==2.8.1
pyodbc==4.0.30
pytz==2020.1
sqlparse==0.3.1这是我在settings.py中的配置:
DATABASES = {
'default': {
'ENGINE': 'sql_server.pyodbc',
'NAME': 'DBNAME',
'USER': 'DBUSER',
'PASSWORD': 'PASSWORD',
'HOST': 'databasename.database.windows.net',
'PORT': '1433',
'OPTIONS': {
'driver': 'ODBC Driver 17 for SQL Server',
},
},
}错误是当我尝试运行'manage.py migrate`时。一切运行正常,直到第8步。以下是输出:
(venv) C:\Users\...\...\>python manage.py migrate
Operations to perform:
Apply all migrations: admin, auth, contenttypes, sessions
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying contenttypes.0002_remove_content_type_name... OK
Applying auth.0002_alter_permission_name_max_length... OK
Applying auth.0003_alter_user_email_max_length... OK
Applying auth.0004_alter_user_username_opts... OK
Applying auth.0005_alter_user_last_login_null... OK
Applying auth.0006_require_contenttypes_0002... OK
Applying auth.0007_alter_validators_add_error_messages... OK
Applying auth.0008_alter_user_username_max_length...Traceback (most recent call last):
File "manage.py", line 22, in <module>
main()
File "manage.py", line 18, in main
execute_from_command_line(sys.argv)
File "C:\Users\...\...\lib\site-packages\django\core\management\__init__.py", line 401, in execute_from_command_line
utility.execute()
File "C:\Users\...\...\lib\site-packages\django\core\management\__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "C:\Users\...\...\lib\site-packages\django\core\management\base.py", line 330, in run_from_argv
self.execute(*args, **cmd_options)
File "C:\Users\...\...\lib\site-packages\django\core\management\base.py", line 371, in execute
output = self.handle(*args, **options)
File "C:\Users\...\...\lib\site-packages\django\core\management\base.py", line 85, in wrapped
res = handle_func(*args, **kwargs)
File "C:\Users\...\...\lib\site-packages\django\core\management\commands\migrate.py", line 243, in handle
post_migrate_state = executor.migrate(
File "C:\Users\...\...\lib\site-packages\django\db\migrations\executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "C:\Users\...\...\lib\site-packages\django\db\migrations\executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "C:\Users\...\...\lib\site-packages\django\db\migrations\executor.py", line 227, in apply_migration
state = migration.apply(state, schema_editor)
File "C:\Users\...\...\lib\site-packages\django\db\migrations\migration.py", line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "C:\Users\...\...\lib\site-packages\django\db\migrations\operations\fields.py", line 236, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "C:\Users\...\...\lib\site-packages\django\db\backends\base\schema.py", line 571, in alter_field
self._alter_field(model, old_field, new_field, old_type, new_type,
File "C:\Users\...\...\lib\site-packages\sql_server\pyodbc\schema.py", line 479, in _alter_field
self.execute(self._create_unique_sql(model, columns=[old_field.column]))
File "C:\Users\...\...\lib\site-packages\sql_server\pyodbc\schema.py", line 861, in execute
sql = str(sql)
File "C:\Users\...\...\lib\site-packages\django\db\backends\ddl_references.py", line 200, in __str__
return self.template % self.parts
KeyError: 'deferrable'
(venv) C:\Users\...\...>但是如果我连接到DB,我看到一个表从Django创建了一个表。
请帮帮忙,谢谢!
发布于 2020-09-16 16:43:24
django-mssql-backend目前支持直到Django 3.0.10。临时的修复方法是将你的Django版本从Django 3.1.x降级到3.0.10。
在此处提出错误请求:https://github.com/ESSolutions/django-mssql-backend/issues/63
编辑:
另一种解决方案,使用Django微软官方的Django支持包来克服所有的问题,支持非常好。
发布于 2020-08-07 02:52:02
今天我遇到了同样的问题。回滚到Django 3.0.x (我返回到3.0.6),然后运行迁移。
我知道这不是一个解决办法,但至少它是一个让你继续前进的工作。一旦您迁移,您应该能够更新回3.1,它将运行良好。
https://stackoverflow.com/questions/63282351
复制相似问题