django.db.utils.OperationalError: 沒有這樣的表

Question

我正在將一個 Django 項目從 1.8 升級到 1.9，我刪除了數據庫文件和所有緩存文件，然后我嘗試運行

python manage.py migrate

或者

python manage.py migrate --run-syncdb

但總是引發此錯誤django.db.utils.OperationalError: no such table:

這是完整的回溯

Traceback (most recent call last):


File "manage.py", line 25, in <module>
    execute_from_command_line(sys.argv)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 350, in execute_from_command_line
    utility.execute()
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 342, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/management/base.py", line 348, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/management/base.py", line 398, in execute
    self.check()
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/management/base.py", line 426, in check
    include_deployment_checks=include_deployment_checks,
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/checks/registry.py", line 75, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/checks/urls.py", line 10, in check_url_config
    return check_resolver(resolver)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/checks/urls.py", line 19, in check_resolver
    for pattern in resolver.url_patterns:
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 417, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/core/urlresolvers.py", line 410, in urlconf_module
    return import_module(self.urlconf_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/basha/UpgradeMloss/mloss/urls.py", line 30, in <module>
    (r'^community/', include('community.urls')),
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/conf/urls/__init__.py", line 52, in include
    urlconf_module = import_module(urlconf_module)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/home/basha/UpgradeMloss/mloss/community/urls.py", line 32, in <module>
    'extra_context' : get_latest_news()
  File "/home/basha/UpgradeMloss/mloss/community/summary.py", line 68, in get_latest_news
    latest_posts = get_latest_posts()
  File "/home/basha/UpgradeMloss/mloss/community/summary.py", line 32, in get_latest_posts
    for forum in all_forums:
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/models/query.py", line 258, in __iter__
    self._fetch_all()
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/models/query.py", line 1074, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/models/query.py", line 52, in __iter__
    results = compiler.execute_sql()
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 852, in execute_sql
    cursor.execute(sql, params)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 79, in execute
    return super(CursorDebugWrapper, self).execute(sql, params)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/utils.py", line 95, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/home/basha/UpgradeMloss/venv1.9/local/lib/python2.7/site-packages/django/db/backends/sqlite3/base.py", line 323, in execute
    return Database.Cursor.execute(self, query, params)
django.db.utils.OperationalError: no such table: community_forum

它在django1.8上運行良好，沒有任何錯誤！ 我應該在Settings.py中進行任何編輯或更新嗎？

Answer 1

這個問題與您的升級無關。 您在urls.py中有一個查詢，在其中執行'extra_context' : get_latest_news() 。 URL導入后立即執行； 因此遷移永遠不會有機會運行。

請注意，除了阻止遷移外，此代碼還會為您提供過時的結果，原因相同：在導入時執行，而不是在運行請求時執行。 刪除該查詢並將其移至視圖本身。

但是，您實際上不應該刪除數據庫或遷移文件。

Answer 2

python3 manage.py makemigrations或python manage.py makemigrations

我做了python3 manage.py migrate --fake或python manage.py migrate --fake 。

它以某種方式起作用。 在我注釋掉ForeignKey 、 ForeignKey 的 model 和 admin.py 中的model之后，我做了這個假遷移。 然后我去管理員那里看了看，外鍵 model不見了。 所以我確實添加了ForeignKey ， model 和admin.site.register並進行了真正的遷移，錯誤消失了。