Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/python/334.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181

Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/django/22.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Python django 1.8.5迁移AbstractUser模型失败_Python_Django_Migration - Fatal编程技术网

Python django 1.8.5迁移AbstractUser模型失败

Python django 1.8.5迁移AbstractUser模型失败,python,django,migration,Python,Django,Migration,将项目从django 1.7.4迁移到1.8.5时,我遇到了一个奇怪的问题 在我的项目中,我扩展了基本用户模型,如下所示: 应用程序用户: class User(AbstractUser): age = models.IntegerField() def __unicode__(self): return self.username 现在,由于某些原因,在django 1.8.5中迁移时,我必须从 python manage.py makemigrations

将项目从django 1.7.4迁移到1.8.5时,我遇到了一个奇怪的问题

在我的项目中,我扩展了基本用户模型,如下所示:

应用程序用户:

class User(AbstractUser):
    age = models.IntegerField()

    def __unicode__(self):
        return self.username
现在,由于某些原因,在django 1.8.5中迁移时,我必须从

python manage.py makemigrations
这将为用户应用程序进行迁移

如果我这样做

 python manage.py migrate
在此之后,它会直接失败并出现此错误

django.db.utils.ProgrammingError: relation "users_user" does not exist
那么我会:

python manage.py migrate users
哪个失败了

"Error creating new content types. Please make sure contenttypes "
RuntimeError: Error creating new content types. Please make sure 
contenttypes is migrated before trying to migrate apps individually.
有趣的是,即使失败了,现在仍在运行

python manage.py migrate
工作

Operations to perform:
  Synchronize unmigrated apps: messages, staticfiles, django_extensions, allauth, avatar, crispy_forms, debug_toolbar
  Apply all migrations: sessions, users, contenttypes, admin, sites, account, auth, socialaccount
Synchronizing apps without migrations:
  Creating tables...
    Creating table avatar_avatar
    Running deferred SQL...
  Installing custom SQL...
Running migrations:
  Rendering model states... DONE
  Applying account.0001_initial... OK
  Applying account.0002_email_max_length... OK
  Applying admin.0001_initial... OK
  Applying contenttypes.0002_remove_content_type_name... OK
  Applying auth.0002_alter_permission_name_max_length... OK
  Applying auth.0003_alter_user_email_max_length... OK
  Applying auth.0004_alter_user_username_opts... OK
  Applying auth.0005_alter_user_last_login_null... OK
  Applying auth.0006_require_contenttypes_0002... OK
  Applying sessions.0001_initial... OK
  Applying sites.0001_initial... OK
  Applying sites.0002_set_site_domain_and_name... OK
  Applying sites.0003_auto_20151104_1309... OK
  Applying socialaccount.0001_initial... OK
从较旧的django版本迁移到1.8版时,是否有人遇到过同样的问题

contenttypes在尝试单独迁移应用程序之前被迁移

您所需要做的就是添加依赖项,以便您的迁移能够按顺序运行


查看一下
django.contrib.contenttypes.migrations
,在
account.migrations
中添加最新的一个作为依赖项,它应该可以正常工作。

感谢您的关注。然而,现在我得到了另一个错误,“关系django_站点不存在”。但这解决了我所问的问题。我将不得不研究另一个(祝你好运:)-我认为需要研究的是:缺少的应用程序(contrib.something?),任何正在进行时髦的代码检查/模型加载的应用程序(如django调试工具栏)以及依赖项。