从 Django 1.6 升级到 1.9：python manage.py migrate 失败

Posted 2023-02-24

【中文标题】从 Django 1.6 升级到 1.9：python manage.py migrate 失败

【英文标题】：Upgrading from Django 1.6 to 1.9: python manage.py migrate failure

【发布时间】：2016-10-10 03:10:27

【问题描述】：

我在生产环境中运行 Django 1.6.6，最近在临时（开发服务器）上升级到 1.9.7。此更新是在服务器上执行的，我按照此处列出的步骤Upgrading from South。

我注意到迁移文件的结构发生了变化，它们不再包含create 语句。这会导致问题，因为如果我从 GitHub 存储库中提取此新代码并运行 python manage.py makemigrations 或 python manage.py migrate，它会显示：

django.db.utils.OperationalError: no such table: appname_modelname

回溯指向我的 urls.py，因为我在查询集中引用了模型：

queryset=list(chain(models.modelname.objects.filter(booleanField=True).order_by(object), models.aDifferentModel.objects.all())),

在 1.9 升级之前，syncdb 为我创建了表，但 migrate 并非如此。我也试过python manage.py migrate --run-syncdb，但这给出了同样的错误。

但是，如果我将 SQLite 数据库从生产或暂存环境复制到本地计算机并运行命令，它就可以工作（因为表已经在数据库中）。

我必须手动创建这些表（尽管我假设不是）还是我做错了什么？

编辑：添加了代码 sn-ps 和回溯。很抱歉最初没有这样做。

models.py

class HowToApply(models.Model):
    title = models.CharField(max_length=500, blank=True, null=True)
    notice = models.TextField(blank=True, null=True)
description = models.TextField(blank=True, null=True)
active = models.BooleanField(default=None)
image = models.FileField(upload_to='numeric/img/%Y', blank=True, null=True)
mobile_image = models.FileField(upload_to='mobile/img/%Y', blank=True, null=True)
sequence_number = models.IntegerField(unique=True)

...

urls.py

from django.conf.urls import patterns, include, url
from django.views.generic import RedirectView, TemplateView, ListView, CreateView
from numeric import models, forms, views
from honeypot.decorators import check_honeypot
from numeric.views import CheckDeviceView
from itertools import chain

urlpatterns = patterns('',
    url(r'^academy/howtoapply/$',
        ListView.as_view(
            queryset =  list(chain(models.HowToApply.objects.filter(active=True).order_by('sequence_number'), models.AcademyAdmin.objects.all())),
        template_name = 'numeric/apply.html'
    ),
    name='apply'),

...

追溯

Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 350, in execute_from_command_line
    utility.execute()
  File "/var/www/website_mig/venv/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 "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 348, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 398, in execute
    self.check()
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/management/base.py", line 426, in check
    include_deployment_checks=include_deployment_checks,
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/checks/registry.py", line 75, in run_checks
    new_errors = check(app_configs=app_configs)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/checks/urls.py", line 10, in check_url_config
    return check_resolver(resolver)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/core/checks/urls.py", line 19, in check_resolver
    for pattern in resolver.url_patterns:
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/var/www/website_mig/venv/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 "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/utils/functional.py", line 33, in __get__
    res = instance.__dict__[self.name] = self.func(instance)
  File "/var/www/website_mig/venv/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 "/var/www/website_mig/project/urls.py", line 14, in <module>
    (r'^', include('numeric.urls')),
  File "/var/www/website_mig/venv/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 "/var/www/website_mig/numeric/urls.py", line 144, in <module>
    queryset = list(chain(models.HowToApply.objects.filter(active=True).order_by('sequence_number'), models.AcademyAdmin.objects.all())),
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/models/query.py", line 258, in __iter__
    self._fetch_all()
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/models/query.py", line 1074, in _fetch_all
    self._result_cache = list(self.iterator())
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/models/query.py", line 52, in __iter__
    results = compiler.execute_sql()
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/models/sql/compiler.py", line 852, in execute_sql
    cursor.execute(sql, params)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/utils.py", line 95, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/var/www/website_mig/venv/local/lib/python2.7/site-packages/django/db/backends/utils.py", line 64, in execute
    return self.cursor.execute(sql, params)
  File "/var/www/website_mig/venv/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: numeric_howtoapply`

【问题讨论】：

migrate 管理命令绝对应该为您创建表。为什么在尝试运行迁移时urls.py 甚至会被导入？

你试过python manage.py makemigrations <app_name>吗？

你绝对不应该在你的 urls.py 中进行查询。

在升级到 1.9 之前，您应该逐步升级（首先是 1.7，然后是 1.8）。它会让它更加更容易

而不是像“django.db.utils.OperationalError: no such table: appname_modelname”这样的虚假错误消息，你为什么不发布完整的错误跟踪？

【参考方案1】：

问题是当urls.py 加载时，您的查询集正在被评估。当您为新项目运行makemigrations 时，这会导致错误，因为尚未创建表。

您可以通过继承 ListView 并将查询集移动到 get_queryset 来解决此问题。

class MyListView(ListView):
    template_name = 'numeric/apply.html'

    def get_queryset(self):
        return list(chain(models.HowToApply.objects.filter(active=True).order_by('sequence_number'), models.AcademyAdmin.objects.all()))

然后更改您的 url 模式以使用您的新视图。

url(r'^academy/howtoapply/$',
    MyListView.as_view(),
    name='apply',
),

Django 1.9 运行一些检查来验证您的 url 模式，这意味着 url 模式在 makemigrations 命令运行之前加载。 Django 1.8 没有这些检查，因此您可以像以前一样设置查询集。

【讨论】：

这个解决方案很完美！非常感谢！

我遇到了同样的问题，但方式略有不同。检查加载urls.py，然后加载views.py，然后加载forms.py，然后其中一个表单具有ModelChoiceField，这会由于queryset参数而导致异常。有没有办法解决这个问题？ ModelChioceFields 查询集是否应该在 Django 1.9 中以不同方式处理？

@thelinuxer 据我所知，ModelChoiceFields 应该不会造成问题。我会问一个新问题并包含代码和回溯。

我发现我的问题与 ModelChoiceField 的初始属性有关。将这些移到表单的 init 中，现在一切正常。

很高兴我能帮上忙 :)