sqlite3.0perationalError: no such column:’test’

python 入门到放弃18.2.5迁移Entry失败

下面是报错内容

Apply all migrations: admin, auth, contenttypes, learning_logs, sessions
Running migrations:
  Applying learning_logs.0002_remove_topic_test_topic_text_entry...Traceback (most recent call last):
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\sqlite3\base.py", line 357, in execute
    return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: no such column: "test"

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "D:\Pycharmproject\learning_log\manage.py", line 22, in <module>
    main()
  File "D:\Pycharmproject\learning_log\manage.py", line 18, in main
    execute_from_command_line(sys.argv)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\__init__.py", line 440, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\base.py", line 402, in run_from_argv
    self.execute(*args, **cmd_options)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\base.py", line 448, in execute
    output = self.handle(*args, **options)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\base.py", line 96, in wrapped
    res = handle_func(*args, **kwargs)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\core\management\commands\migrate.py", line 349, in handle
    post_migrate_state = executor.migrate(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\migrations\executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\migrations\executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\migrations\executor.py", line 252, in apply_migration
    state = migration.apply(state, schema_editor)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\migrations\migration.py", line 130, in apply
    operation.database_forwards(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\migrations\operations\fields.py", line 170, in database_forwards
    schema_editor.remove_field(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\sqlite3\schema.py", line 421, in remove_field
    super().remove_field(model, field)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\base\schema.py", line 724, in remove_field
    self.execute(sql)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\base\schema.py", line 199, in execute
    cursor.execute(sql, params)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 102, in execute
    return super().execute(sql, params)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 67, in execute
    return self._execute_with_wrappers(
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
  File "D:\Pycharmproject\learning_log\ll_env\lib\site-packages\django\db\backends\sqlite3\base.py", line 357, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such column: "test"


百度了很多不知道怎么办

该错误提示表明,在执行SQL查询时找不到名为 "test" 的列。这通常发生在迁移数据库时,因为可能已经更改了数据库结构,而迁移代码中未能正确反映这些更改。

要解决此问题,请按照以下步骤操作:

  • 确认数据库表结构:检查数据库表结构,确保表中确实有名为 "test" 的列。如果没有,请更新表结构以包含所需的列。

  • 执行数据库迁移:运行数据迁移代码,以确保数据库结构与应用程序代码中的结构相匹配。

  • 检查迁移代码:检查数据迁移代码,查看是否正确地更新了数据库结构。确保在修改表结构时,相应的迁移代码也已更新。

  • 重新运行应用程序:如果您已经修改了数据库结构并重新运行了迁移代码,可以尝试重新运行应用程序,看看是否成功。

不知道你这个问题是否已经解决, 如果还没有解决的话:

如果你已经解决了该问题, 非常希望你能够分享一下解决方案, 写成博客, 将相关链接放在评论区, 以帮助更多的人 ^-^