Question

我最近从django-social-auth切换到python-social-auth，但它明显损害了我的迁移系统。任何时候我尝试迁移更改我得到了这个：

  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 161, in handle
    executor.migrate(targets, plan, fake=options.get("fake", False))
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/migrations/executor.py", line 68, in migrate
    self.apply_migration(migration, fake=fake)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/migrations/executor.py", line 102, in apply_migration
    migration.apply(project_state, schema_editor)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/migrations/migration.py", line 108, in apply
    operation.database_forwards(self.app_label, schema_editor, project_state, new_state)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/migrations/operations/fields.py", line 139, in database_forwards
    schema_editor.alter_field(from_model, from_field, to_field)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/backends/schema.py", line 457, in alter_field
    self._alter_field(model, old_field, new_field, old_type, new_type, old_db_params, new_db_params, strict)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/backends/schema.py", line 603, in _alter_field
    params,
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/backends/schema.py", line 103, in execute
    cursor.execute(sql, params)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/backends/utils.py", line 65, in execute
    return self.cursor.execute(sql, params)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/utils.py", line 94, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/app/.heroku/python/lib/python2.7/site-packages/django/db/backends/utils.py", line 65, in execute
    return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: relation "social_auth_code" does not exist

问题是它只发生在我的应用程序的生产版本中，并且出于其他原因，我不得不删除我过去的迁移文件。不容易调查。无论如何，它现在完全适用于我的开发应用程序，但我无法弄清楚生产中可能出现的问题，我尝试了所有＆＃34;伪造迁移＆＃34;世界上的伎俩似乎没什么用。

网络上唯一的地方是我能找到这样的错误there 但我从未使用南方，所以第一个答案对我不起作用。直接挖掘迁移表并发送原始SQL指令可能是解决方案，但由于它是在我的生产版本中，我不觉得修补db（我有成千上万的注册用户，有数据和所有.. ）。简而言之，我深入了解了*。另外，我不知道使用哪个命令直接访问db ...

中的迁移表

任何能够保证我的数据安全的解决方案都非常受欢迎：））

Answer 1

迁移到python_social_auth时，我遇到了同样的错误。这对Django 1.8很有用。也许我的解决方案会帮助你：

虚假迁移python_social_auth的首字母

python manage.py migrate default 0001 --fake

为初始psa创建自己的迁移并将其放入/your_project/your_app/migrations/0009_migrate_to_psa.py:

# -*- coding: utf-8 -*-
from __future__ import unicode_literals

from django.db import models, migrations
import social.apps.django_app.default.fields
from django.conf import settings
import social.storage.django_orm
from social.utils import setting_name

user_model = getattr(settings, setting_name('USER_MODEL'), None) or \
             getattr(settings, 'AUTH_USER_MODEL', None) or \
             'auth.User'


class Migration(migrations.Migration):

    dependencies = [
        migrations.swappable_dependency(user_model),
        ('your_app', '0008_last_migration_in_your_app'),
        ('default', '0001_initial'),
    ]

    operations = [
        migrations.CreateModel(
            name='Code',
            fields=[
                ('id', models.AutoField(
                    verbose_name='ID', serialize=False, auto_created=True,
                    primary_key=True)),
                ('email', models.EmailField(max_length=75)),
                ('code', models.CharField(max_length=32, db_index=True)),
                ('verified', models.BooleanField(default=False)),
            ],
            options={
                'db_table': 'social_auth_code',
            },
            bases=(models.Model, social.storage.django_orm.DjangoCodeMixin),
        ),
        migrations.AlterUniqueTogether(
            name='code',
            unique_together=set([('email', 'code')]),
        ),
    ]

注意依赖项：

dependencies = [
    migrations.swappable_dependency(user_model),
    ('your_app', '0008_last_migration_in_your_app'),
    ('default', '0001_initial'),
]

迁移您的项目
```
python manage.py migrate your_app
```
并迁移所有
```
python manage.py migrate
```

<强>更新不幸的是，这种方法需要在models.py文件中使用模型代码。否则，在下一个操作makemigrations时，将从数据库中删除该表。 /your_project/your_app/models.py：

from social.storage.django_orm import DjangoCodeMixin
class Code(models.Model, DjangoCodeMixin):
    email = models.EmailField(max_length=254)
    code = models.CharField(max_length=32, db_index=True)
    verified = models.BooleanField(default=False)

    class Meta:
        db_table = 'social_auth_code'
        unique_together = ('email', 'code')

Answer 2

我以前尝试运行该解决方案，但对依赖项有一些困难。我最终只是将以下几行添加到迁移Migration.operations中的0007_code_timestamp列表的前面（与原始first answer suggested完全一样）

        migrations.CreateModel(                                                 
            name='Code',                                                        
            fields=[                                                            
                ('id', models.AutoField(                                        
                    verbose_name='ID', serialize=False, auto_created=True,      
                    primary_key=True)),                                         
                ('email', models.EmailField(max_length=75)),                    
                ('code', models.CharField(max_length=32, db_index=True)),       
                ('verified', models.BooleanField(default=False)),               
            ],                                                                  
            options={                                                           
                'db_table': 'social_auth_code',                                 
            },                                                                  
            bases=(models.Model, social_django.storage.DjangoCodeMixin),        
        ),                                                                      
        migrations.AlterUniqueTogether(                                         
            name='code',                                                        
            unique_together=set([('email', 'code')]),                           
        ),

并确保位于顶部的import social_django。

为我解决了这个问题，这比创建新迁移和处理依赖关系澄清要容易得多。

＆＃34;关系＆＃34; social_auth_code＆＃34;不存在＆＃34;在django

2 个答案: