django 2.2 migrate gets error “table already exists” django.db.utils.ProgrammingError: 1146 的解决办法

最新推荐文章于 2025-06-12 08:14:46 发布
最新推荐文章于 2025-06-12 08:14:46 发布
阅读量266 收藏
点赞数
CC 4.0 BY-SA版权
分类专栏： python 文章标签： python django
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/mdllll/article/details/108526854
当常规方法无法解决问题时，本文分享了一种通过导出数据库数据，重建数据库并执行Python迁移脚本来解决数据库问题的经验。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

网上的方法：
方法1

但这方法对我不管用
最后我把数据库里面的数据导出来后，重建新的数据库，再执行

python manage.py makemigrations 
python manage.py migrate

才可以……

Django migrate django.db.utils.OperationalError: (1050, “Table ‘xxx‘ already exists“)
YOU CAN IF YOU BELIEVE YOU CAN
07-12 242
Django migrate django.db.utils.OperationalError: (1050, "Table 'xxx' already exists")
（Django）Web网页导入pycharm时遇到的问题集合（备份）
weixin_47401619的博客
05-12 3956
（Django）Web网页导入pycharm时遇到的问题集合
django.db.utils.ProgrammingError: (1146, u“Table‘’ doesn’t exist”)问题的解决
09-20
主要给大家介绍了关于执行python manage.py migrate时报错：django.db.utils.ProgrammingError: (1146, "Table 'test.model_student' doesn't exist" )问题的解决方法，文中将解决的方法介绍的非常详细，需要的朋友可以参考下
解决django迁移数据库时，报错django.db.utils.InternalError: (1050, “Table ‘xxx‘ already exists“)
weixin_44575037的博客
10-14 683
先上报错 django.db.utils.InternalError: (1050, "Table 'xxx' already exists") 按照下面步骤依次执行 python manage.py showmigrations #显示迁移的内容 下面的core是你项目中生成迁移文件的子应用名称 python manage.py migrate --fake core zero #清除迁移历史 再次查看会发现这个子应用下的迁移文件记录已经清除了 python manage.py showmigratio
django.db.utils.ProgrammingError: (1146, "Table 'xxxxxx' doesn't exist")
、Edgar的博客
01-25 582
将目录migrations下的文件除了__init__.py都删掉，如下： 然后再次执行： python manage.py makemigrations python manage.py migrate
ERROR: relation “xxx“ already exists
goddave的博客
01-21 1万+
我发生这个问题是导入了一个表的备份sql之后，将其重命名了，然后又导入了这个表的时候发生的。 报错后去备份的sql中查看这个relation的关键字，发现了这样一条约束： 原来是这个表在添加的时候，已经对这个表的id主键增加了这个名称的约束，虽然更改了表名，但是约束名称没有变，因此重新导入这个表，虽然2个表名不同了，但是都存在这个名称的约束，所以导入失败。 解决方法： 去除原来的约束，或者修改导入新表或者旧表的sql中这个约束的名称，重新添加约束即可。 ...
（Django）Web网页导入pycharm时遇到的问题集合
weixin_47401619的博客
06-21 2846
pycharm+html
Django中数据库迁移失败的报错与修复
最新发布
shejizuopin的博客
06-12 571
本文总结了Django数据库迁移失败的常见问题及解决方案。主要包括：1)数据库连接错误，需检查配置参数；2)模型与数据库模式不一致，需调整表结构或使用--fake参数；3)迁移文件错误，需检查语法或设置默认值；4)数据库锁定，需等待或重启服务；5)循环依赖，需重构模型关系。文中提供了详细的错误示例、修复方法和代码实例，并整理成问题-解决方案对照表。通过系统性的排查和修复技巧，可以有效解决迁移问题，确保数据库结构正常更新。
(.venv) PS D:\pycharm\daima\fg\login_reg> python manage.py migrate Operations to perform: Apply all migrations: admin, auth, contenttypes, login, sessions Running migrations: Traceback (most recent call last): File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 82, in _execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute return self.cursor.execute(query, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\cursors.py", line 153, in execute result = self._query(query) ^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\cursors.py", line 322, in _query conn.query(q) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 563, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 825, in _read_query_result result.read() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 1199, in read first_packet = self.connection._read_packet() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 775, in _read_packet packet.raise_for_error() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\migrations\recorder.py", line 67, in ensure_schema editor.create_model(self.Migration) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\base\schema.py", line 307, in create_model self.execute(sql, params or None) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\base\schema.py", line 137, in execute cursor.execute(sql, params) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 99, in execute return super().execute(sql, params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 67, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 76, in _execute_with_wrappers return executor(sql, params, many, context) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 80, in _execute with self.db.wrap_database_errors: File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\utils.py", line 89, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\utils.py", line 82, in _execute return self.cursor.execute(sql) ^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute return self.cursor.execute(query, args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\cursors.py", line 153, in execute result = self._query(query) ^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\cursors.py", line 322, in _query conn.query(q) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 563, in query self._affected_rows = self._read_query_result(unbuffered=unbuffered) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 825, in _read_query_result result.read() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 1199, in read first_packet = self.connection._read_packet() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\connections.py", line 775, in _read_packet packet.raise_for_error() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\protocol.py", line 219, in raise_for_error err.raise_mysql_exception(self._data) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\pymysql\err.py", line 150, in raise_mysql_exception raise errorclass(errno, errval) django.db.utils.ProgrammingError: (1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1") During handling of the above exception, another exception occurred: Traceback (most recent call last): File "D:\pycharm\daima\fg\login_reg\manage.py", line 21, in <module> main() File "D:\pycharm\daima\fg\login_reg\manage.py", line 17, in main execute_from_command_line(sys.argv) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\__init__.py", line 381, in execute_from_command_line utility.execute() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\__init__.py", line 375, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\base.py", line 323, in run_from_argv self.execute(*args, **cmd_options) File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\base.py", line 364, in execute output = self.handle(*args, **options) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\base.py", line 83, in wrapped res = handle_func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\core\management\commands\migrate.py", line 232, in handle post_migrate_state = executor.migrate( ^^^^^^^^^^^^^^^^^ File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\migrations\executor.py", line 91, in migrate self.recorder.ensure_schema() File "D:\pycharm\daima\fg\.venv\Lib\site-packages\django\db\migrations\recorder.py", line 69, in ensure_schema raise MigrationSchemaMissing("Unable to create the django_migrations table (%s)" % exc) django.db.migrations.exceptions.MigrationSchemaMissing: Unable to create the django_migrations table ((1064, "You hav e an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '(6) NOT NULL)' at line 1"))
06-03
### 解决 Django 项目中执行 `migrate` 命令时出现 SQL 语法错误 (1064) 的问题 在 Django 项目中，当执行 `python manage.py migrate` 命令时，如果出现 SQL 语法错误 `(1064, "You have an error in your SQL ...
mysql数据库报错1064_Django链接mysql数据库报错1064
weixin_35143292的博客
01-19 536
D:\PycharmProjects\autotest>python manage.py makemigrationsdjango.db.utils.ProgrammingError: (1064, "You have an error in your SQL syntax;check the manual that corresponds to your MySQL server vers...
python manage.py migrate 出错 django.db.utils.ProgrammingError
jaket5219999的博客
03-17 6519
django migrate 出错 django.db.utils.ProgrammingError: (1146, u"Table 'myblog2.blog_article' doesn't exist") 在用django写一个博客系统时，自动创建数据库表格，出现上述错误 python manage.py makemigrations Migrations for 'blog':
django连接mysql数据库1064错误
画流_博客
12-07 1781
错误信息如下 django.db.utils.ProgrammingError: (1064, “You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘SET SESSION TRANSACTION ISOLATION LEVEL READ COMMITTED’ at line 1”) 原因：
Django异常--django.db.utils.ProgrammingError: (1146, "Table '项目名.xxx' doesn't exist")
wys578的博客
07-16 6496
  问题：项目新建，运行时可能会报这种系列的异常：django.db.utils.ProgrammingError: (1146, "Table '项目名.xxx' doesn't exist") 首先，试试统一执行迁移： python manage.py makemigrations python manage.py migrate 如果上面的命令未解决问题，则： 将settings....
django.db.utils.ProgrammingError: 1146 的解决办法
weixin_33787529的博客
04-26 3044
在models中设置完数据库相关的东西后执行命令 python manage.py makemigrations 此处无错误 再次执行 python manage.py migrate 发生报错 错误信息很长，仔细查找，发现错误根源 django.db.utils.ProgrammingError: (1146, "Table 'test.mod...
django.db.utils.ProgrammingError: (1146, “Table ‘xxx’ doesn’t exist”) 解决方法
热门推荐
Wonz
12-14 2万+
django.db.utils.ProgrammingError: (1146, "Table 'tmsdata.sysMgr_syslog' doesn't exist")
django.db.utils.ProgrammingError: (1146, "Table 'userdb.materialdb_userdb' doesn't exist")
younger_to_older的博客
08-23 698
*** 1146，数据库库不存在 只需要两条命令解决 第一步： 先在terminal运行程序： 然后访问界面，和预期一样报错 具体原因是当你运行人的项目时没有迁移django内库 按接下面两条语句执行： python3 manage.py makemigrations python3 manage.py migrate 执行后查看数据库如下： 再次运行就可以正常访问了 如果解决了你的...
django.db.utils.ProgrammingError: (1146, u"Table'' doesn't exist")解决办法
Twiss的博客
12-27 1546
在django中执行数据库迁移命令时出错： django.db.utils.ProgrammingError: (1146, u&quot;Table’’ doesn’t exist&quot;)解决办法 解决办法如下： 一、现象 在数据库中删除了一张表，重新执行python manage.py migrate时出错，提示不存在这张表。 二、原因 主要是因为django一般在第一次迁移的时候新建表，后面的都不会新建表...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值