将现有 auth.User 数据迁移到新的 Django 1.5 自定义用户模型

南方完全有能力为您完成这次迁移，但您需要聪明一点，分阶段进行.下面是分步指南:(本指南假定您有AbstractUser个子类，而不是AbstractBaseUser个子类)

1. 在进行切换之前，请确保在应用程序中启用了SOUTH支持 它包含您的自定义用户模型(出于指南的目的，我们将其命名为accounts和模型User). 在这一点上，您应该有一个自定义的用户模型not yet.

   $ ./manage.py schemamigration accounts --initial
   Creating migrations directory at 'accounts/migrations'...
   Creating __init__.py in 'accounts/migrations'...
   Created 0001_initial.py.
   
   $ ./manage.py migrate accounts [--fake if you've already syncdb'd this app]
    Running migrations for accounts:
    - Migrating forwards to 0001_initial.
    > accounts:0001_initial
    - Loading initial data for accounts.
   

2. 在accounts应用程序中创建一个新的空白用户migrations.

   $ ./manage.py schemamigration accounts --empty switch_to_custom_user
   Created 0002_switch_to_custom_user.py.
   

3. 在accounts应用程序中创建自定义User型号，但确保将其定义为:

   class SiteUser(AbstractUser): pass
   

4. 使用以下代码填充空白migrations.

   # encoding: utf-8
   from south.db import db
   from south.v2 import SchemaMigration
   
   class Migration(SchemaMigration):
   
       def forwards(self, orm):
           # Fill in the destination name with the table name of your model
           db.rename_table('auth_user', 'accounts_user')
           db.rename_table('auth_user_groups', 'accounts_user_groups')
           db.rename_table('auth_user_user_permissions', 'accounts_user_user_permissions')
   
       def backwards(self, orm):
           db.rename_table('accounts_user', 'auth_user')
           db.rename_table('accounts_user_groups', 'auth_user_groups')
           db.rename_table('accounts_user_user_permissions', 'auth_user_user_permissions')
   
       models = { ....... } # Leave this alone
   

5. 运行迁移

   $ ./manage.py migrate accounts
    - Migrating forwards to 0002_switch_to_custom_user.
    > accounts:0002_switch_to_custom_user
    - Loading initial data for accounts.
   

6. 现在对您的用户模型进行任何更改.

   # settings.py
   AUTH_USER_MODEL = 'accounts.User'
   
   # accounts/models.py
   class SiteUser(AbstractUser):
       site = models.ForeignKey(Site, null=True)
   

7. 为此更改创建并运行迁移

   $ ./manage.py schemamigration accounts --auto
    + Added field site on accounts.User
   Created 0003_auto__add_field_user_site.py.
   
   $ ./manage.py migrate accounts
    - Migrating forwards to 0003_auto__add_field_user_site.
    > accounts:0003_auto__add_field_user_site
    - Loading initial data for accounts.
   

老实说，如果你已经对你的设置有了很好的了解，并且已经使用了south，那么它应该很简单，只需将以下迁移添加到你的accounts模块中即可.

# encoding: utf-8
from south.db import db
from south.v2 import SchemaMigration
from django.db import models

class Migration(SchemaMigration):

    def forwards(self, orm):
        # Fill in the destination name with the table name of your model
        db.rename_table('auth_user', 'accounts_user')
        db.rename_table('auth_user_groups', 'accounts_user_groups')
        db.rename_table('auth_user_permissions', 'accounts_user_permissions')
        # == YOUR CUSTOM COLUMNS ==
        db.add_column('accounts_user', 'site_id',
            models.ForeignKey(orm['sites.Site'], null=True, blank=False)))

    def backwards(self, orm):
        db.rename_table('accounts_user', 'auth_user')
        db.rename_table('accounts_user_groups', 'auth_user_groups')
        db.rename_table('accounts_user_user_permissions', 'auth_user_user_permissions')
        # == YOUR CUSTOM COLUMNS ==
        db.remove_column('accounts_user', 'site_id')

    models = { ....... } # Leave this alone

2013年2月5日编辑:增加auth_user_group表的重命名.由于数据库约束，FKS将自动更新以指向正确的表，但M2M字段的表名是从2个端表的名称生成的，需要以这种方式手动更新.

编辑2:感谢@Tuttle&；@Pix0r的更正.