在运行manage.py test期间出现了“django.db.utils.ProgrammingError: relation "app_user" does not exist”的错误。

Question

在运行manage.py test期间出现了“django.db.utils.ProgrammingError: relation "app_user" does not exist”的错误。

10

我的设置：

Django 1.8.3
Python 2.7.10
Ubuntu 14.04
django-two-factor-auth==1.2.0

当我运行python manage.py test时，我遇到了以下错误：

Traceback (most recent call last):
  File "/src/venv/bin/django-admin.py", line 5, in <module>
    management.execute_from_command_line()
  File "/src/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
    utility.execute()
  File "/src/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 330, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/commands/test.py", line 30, in run_from_argv
    super(Command, self).run_from_argv(argv)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/base.py", line 393, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/commands/test.py", line 74, in execute
    super(Command, self).execute(*args, **options)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/base.py", line 444, in execute
    output = self.handle(*args, **options)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/commands/test.py", line 90, in handle
    failures = test_runner.run_tests(test_labels)
  File "/src/venv/lib/python2.7/site-packages/django/test/runner.py", line 210, in run_tests
    old_config = self.setup_databases()
  File "/src/venv/lib/python2.7/site-packages/django/test/runner.py", line 166, in setup_databases
    **kwargs
  File "/src/venv/lib/python2.7/site-packages/django/test/runner.py", line 370, in setup_databases
    serialize=connection.settings_dict.get("TEST", {}).get("SERIALIZE", True),
  File "/src/venv/lib/python2.7/site-packages/django/db/backends/base/creation.py", line 368, in create_test_db
    test_flush=not keepdb,
  File "/src/venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 120, in call_command
    return command.execute(*args, **defaults)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/base.py", line 444, in execute
    output = self.handle(*args, **options)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 179, in handle
    created_models = self.sync_apps(connection, executor.loader.unmigrated_apps)
  File "/src/venv/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 317, in sync_apps
    cursor.execute(statement)
  File "/src/venv/lib/python2.7/site-packages/django/db/backends/utils.py", line 65, in execute
    return self.cursor.execute(sql, params)
  File "/src/venv/lib/python2.7/site-packages/django/db/utils.py", line 97, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/src/venv/lib/python2.7/site-packages/django/db/backends/utils.py", line 63, in execute
    return self.cursor.execute(sql)
django.db.utils.ProgrammingError: relation "app_user" does not exist

当我在django/db/backends/utils.py的第62行放置print(sql)语句时，我会得到以下输出：

CREATE DATABASE "test_dev"

            SELECT c.relname, c.relkind
            FROM pg_catalog.pg_class c
            LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
            WHERE c.relkind IN ('r', 'v')
                AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
                AND pg_catalog.pg_table_is_visible(c.oid)
CREATE TABLE "django_migrations" ("id" serial NOT NULL PRIMARY KEY, "app" varchar(255) NOT NULL, "name" varchar(255) NOT NULL, "applied" timestamp with time zone NOT NULL)

            SELECT c.relname, c.relkind
            FROM pg_catalog.pg_class c
            LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
            WHERE c.relkind IN ('r', 'v')
                AND n.nspname NOT IN ('pg_catalog', 'pg_toast')
                AND pg_catalog.pg_table_is_visible(c.oid)
SAVEPOINT "s140275211773760_x1"
CREATE TABLE "distributedlock_lock" ("id" serial NOT NULL PRIMARY KEY, "key" varchar(255) NOT NULL, "value" varchar(255) NOT NULL, "timestamp" timestamp with time zone NULL)
RELEASE SAVEPOINT "s140275211773760_x1"
SAVEPOINT "s140275211773760_x2"
CREATE TABLE "djkombu_queue" ("id" serial NOT NULL PRIMARY KEY, "name" varchar(200) NOT NULL UNIQUE)
RELEASE SAVEPOINT "s140275211773760_x2"
SAVEPOINT "s140275211773760_x3"
CREATE TABLE "djkombu_message" ("id" serial NOT NULL PRIMARY KEY, "visible" boolean NOT NULL, "sent_at" timestamp with time zone NULL, "payload" text NOT NULL, "queue_id" integer NOT NULL)
RELEASE SAVEPOINT "s140275211773760_x3"
SAVEPOINT "s140275211773760_x4"
CREATE TABLE "otp_static_staticdevice" ("id" serial NOT NULL PRIMARY KEY, "user_id" integer NOT NULL, "name" varchar(64) NOT NULL, "confirmed" boolean NOT NULL)
RELEASE SAVEPOINT "s140275211773760_x4"
SAVEPOINT "s140275211773760_x5"
CREATE TABLE "otp_static_statictoken" ("id" serial NOT NULL PRIMARY KEY, "device_id" integer NOT NULL, "token" varchar(16) NOT NULL)
RELEASE SAVEPOINT "s140275211773760_x5"
SAVEPOINT "s140275211773760_x6"
CREATE TABLE "otp_totp_totpdevice" ("id" serial NOT NULL PRIMARY KEY, "user_id" integer NOT NULL, "name" varchar(64) NOT NULL, "confirmed" boolean NOT NULL, "key" varchar(80) NOT NULL, "step" smallint NOT NULL CHECK ("step" >= 0), "t0" bigint NOT NULL, "digits" smallint NOT NULL CHECK ("digits" >= 0), "tolerance" smallint NOT NULL CHECK ("tolerance" >= 0), "drift" smallint NOT NULL, "last_t" bigint NOT NULL)
RELEASE SAVEPOINT "s140275211773760_x6"
CREATE INDEX "djkombu_queue_name_1c24e49fd475ad53_like" ON "djkombu_queue" ("name" varchar_pattern_ops)
ALTER TABLE "djkombu_message" ADD CONSTRAINT "djkombu_message_queue_id_12778caea7843dd_fk_djkombu_queue_id" FOREIGN KEY ("queue_id") REFERENCES "djkombu_queue" ("id") DEFERRABLE INITIALLY DEFERRED
CREATE INDEX "djkombu_message_46cf0e59" ON "djkombu_message" ("visible")
CREATE INDEX "djkombu_message_df2f2974" ON "djkombu_message" ("sent_at")
CREATE INDEX "djkombu_message_75249aa1" ON "djkombu_message" ("queue_id")
ALTER TABLE "otp_static_staticdevice" ADD CONSTRAINT "otp_static_staticdevice_user_id_39a61f1bd3ec970d_fk_app_user_id" FOREIGN KEY ("user_id") REFERENCES "ff_user" ("id") DEFERRABLE INITIALLY DEFERRED

对我来说很明显，在测试数据库设置期间我的测试失败了。具体来说，尝试在 otp_static_staticdevice 表和我的应用程序 app_user 表之间创建外键约束失败。

我立即提出的问题是，为什么 Django 在创建我的应用程序表之前先创建 OTP 表？我的假设是 OTP 应用程序在我的 INSTALLED_APPS 中排名第一。但事实并非如此：

INSTALLED_APPS = [
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.sites',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'django.contrib.admin',
    'django.contrib.humanize',
    'app',
    ...
    'django_otp',
    'django_otp.plugins.otp_static',
    'django_otp.plugins.otp_totp',
    'two_factor',
    ...
]

下一步，我查看 django/core/management/commands/migrate.py 文件，试图找出 Django 如何确定应用程序的迁移顺序。

在第 264 行（https://github.com/django/django/blob/1.8.3/django/core/management/commands/migrate.py#L264）上加入一个 pdb.set_trace() 语句，并查看 app_labels 包含什么，我得到了以下结果：

set(['djangosaml2', 'django_ace', 'recurly', 'staticfiles', 'distributedlock', 'app_overrides', 'messages', 'django_otp', 'kombu_transport_django', 'otp_totp', 'compressor', 'otp_static', 'humanize', 'ajax_select', 'django_extensions', 'import_export', 'raven_compat', 'crispy_forms', 'emoji'])

在我决定请求帮助之前，我已经做到了这一步。是否有人知道Django如何最终不按正确顺序创建所有项目应用程序，以避免出现体面的冲突？

- Paul

1

先尝试运行 ./manage.py makemigrations app 命令，然后再继续。 - itzMEonTV

3

@Paul，你解决了这个问题吗？我也遇到了同样的问题，只是它抱怨了一个不同的关系。 - Helmut

8个回答

7

这个问题可以通过运行以下命令来解决：

python manage.py migrate auth
python manage.py migrate app
python manage.py migrate

- Sebastian Wozny

4

python manage.py migrate auth

这个有效。

- liansheng

2

您没有提供任何代码，因此很难理解您的模型关系。但我可以猜测您是否已将ForeignKey模型作为实例传递？尝试以字符串形式传递它。

class MyModel(models.Model):
    fk_field = models.ForeignKey('path.to.other.model')    # same as from path.models import model

这通常是有效的。希望对你也有用！

- kunl

1

确保您的所有应用程序目录中都有 migrations/ 文件夹和其中的 __init__.py 文件。如果没有，请创建一个 migrations/ 文件夹并在其中创建一个 __init__.py 文件。如果您正在使用 git，请将 !migrations/__init__.py 添加到 .gitignore 文件中。

- ANFAS PV

尝试了其他所有方法，这个方法对我有效。谢谢。 - Ragav Y

1

我曾在GitLab CI作业中运行manage.py test时遇到类似问题，通过在base.py设置文件中创建一个名为CI的变量，我成功解决了这个问题。请注意，需要保留HTML标签。

base.py

"""
Set CI Variable to True when running: "manage.py test"
"""
CI = True

在我的settings.py中：

if CI:
    class DisableMigrations(object):

        def __contains__(self, item):
            return True

        def __getitem__(self, item):
            return None # For Django 1.10+

MIGRATION_MODULES = DisableMigrations()

- jaandaldethu

0

我遇到了同样的错误，因为我的一个Django应用程序没有 migrations 目录。请仔细检查所有在 INSTALLED_APPS 中列出的应用程序文件夹。

- valex

0

在我的情况下，迁移没有运行，因为我使用了 unittest.TestCase 而不是 django.test.TestCase。

解决方案：替换。

from unittest import TestCase

使用

from django.test import TestCase

- Benoit Blanchon

网页内容由stack overflow 提供, 点击上面的

可以查看英文原文，
原文链接

- Diego Ponciano · Accepted Answer

遇到了同样的问题，而且由于它发生在./manage.py test上，你的迁移可能已经损坏。
自Django 1.7以来，有一个名为MIGRATION_MODULES的新设置，你可以在其中配置你的应用程序的迁移模块。
在settings.py中添加以下解决方法(在这里找到)，可以跳过测试中的迁移，并为我解决了这个问题:

class DisableMigrations(object):

    def __contains__(self, item):
        return True

    def __getitem__(self, item):
        return "notmigrations"

MIGRATION_MODULES = DisableMigrations()