Python Django删除了DDBB表，无法再迁移：没有此类表错误

我已经从sqlite DDBB中删除了一个表，因为我想做一些更改，但无法在Django中对模型进行简单的更新。从那时起，我无法再次执行迁移并为我的模型获取一个新表，得到错误django.db.utils.OperationalError:没有这样的表：shop\u productitem

我试图在其他类似的线程中遵循许多提示，但运气不佳。例如，我已经尝试过，但我无法解决这个问题。我的理解是，如果我运行makemigrations，然后迁移模型，ddbb应该用新的规范进行自我更新，但在这个特定的情况下，我可能弄错了

有人能告诉我问题出在哪里吗？我担心我自己没有必要的知识来解决这个问题，我已经找了很久了

请在下面找到我收到的全部错误消息：

    Applying shop.0002_auto_20200218_1958...Traceback (most recent call last):
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py", line 303, in execute
    return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: no such table: shop_productitem

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

Traceback (most recent call last):
  File "manage.py", line 15, in <module>
    execute_from_command_line(sys.argv)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/core/management/__init__.py", line 371, in execute_from_command_line
    utility.execute()
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/core/management/__init__.py", line 365, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/core/management/base.py", line 335, in execute
    output = self.handle(*args, **options)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 200, in handle
    fake_initial=fake_initial,
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/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 "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/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 "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/migrations/executor.py", line 244, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/migrations/migration.py", line 122, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/migrations/operations/fields.py", line 216, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/schema.py", line 133, in alter_field
    super().alter_field(model, old_field, new_field, strict=strict)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 509, in alter_field
    old_db_params, new_db_params, strict)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/schema.py", line 330, in _alter_fi
eld
    self._remake_table(model, alter_field=(old_field, new_field))
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/schema.py", line 260, in _remake_t
able
    disable_constraints=False,
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/schema.py", line 95, in alter_db_t
able
    super().alter_db_table(model, old_db_table, new_db_table)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 383, in alter_db_tab
le
    "new_table": self.quote_name(new_db_table),
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/base/schema.py", line 117, in execute
    cursor.execute(sql, params)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 100, in execute
    return super().execute(sql, params)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 68, in execute
    return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 77, in _execute_with_wrapp
ers
    return executor(sql, params, many, context)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/utils.py", line 85, in _execute
    return self.cursor.execute(sql, params)
  File "/home/EconopecoWebApp/.virtualenvs/django2/lib/python3.6/site-packages/django/db/backends/sqlite3/base.py", line 303, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: shop_productitem

非常感谢你，

---

歪看

您是否尝试过从migrations文件夹中删除每个迁移，除了init，然后运行makemigrations和migrate？

如果您可以承受数据库中的数据丢失，那么只需从其文件夹中删除旧的数据库文件即可。从迁移文件夹中删除所有迁移。然后运行makemigrations和migrate，这将创建新的sqllight数据库

另一个选项如果数据丢失不是一个选项，您可以尝试使用或手动重新创建已删除的表。然后使用迁移正确地删除它们

---

对于将来，若您需要删除表，您应该删除或注释它的模型代码，然后运行makemigrations，migrate，这将正确地从数据库中删除表。所以，仅仅删除文件是不行的。嗨，布鲁诺，如果我这样做，迁移一开始就没有任何错误，但是如果我签入我的管理员并尝试打开productitem，我会在/admin/shop/productitem/没有这样的表：shop\u productitem再次：嗨，weAreStarDust，你能给我一个如何做的提示吗？实际上，我还没有尝试过这样做，这可能是我的出路。许多的thanks@Askew迁移历史记录存储在django_migrations table中我从来没有像weAreStarDust说的那样做过，但从我现在在Postgres中看到的情况来看，有一个名为django_migrations的表，其中记录了完成的所有迁移。您可以尝试截断它。哦，是的，这就是我所做的，我管理了.py dbshell，然后删除了我想要删除的表，然后删除了旧的迁移，然后运行make migrations并再次迁移。一点运气都没有@我提出了两种方案，询问是否有不清楚的地方。我通过命令行手动重新创建了表，并按照您的指示进行了操作，效果非常好。非常感谢你，我被困在这里很久了！非常感谢@Askew很高兴听到这个消息，对数据库的每次操作进行备份是一种很好的做法，这将为您节省大量时间：