我有一个现有的Django项目,我刚刚将其添加到了。
manage.py schemamigration app_name
manage.py migrate app_name --fake
manage.py schemamigration app_name
manage.py migrate app_name
然后我收到了这个:
$ heroku run python notecard/manage.py migrate notecards
Running python notecard/manage.py migrate notecards attached to terminal... up, run.1
Running migrations for notecards:
- Migrating forwards to 0005_initial.
> notecards:0003_initial
Traceback (most recent call last):
File "notecard/manage.py", line 14, in <module>
execute_manager(settings)
File "/app/lib/python2.7/site-packages/django/core/management/__init__.py", line 438, in execute_manager
utility.execute()
File "/app/lib/python2.7/site-packages/django/core/management/__init__.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/app/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File "/app/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
output = self.handle(*args, **options)
File "/app/lib/python2.7/site-packages/south/management/commands/migrate.py", line 105, in handle
ignore_ghosts = ignore_ghosts,
File "/app/lib/python2.7/site-packages/south/migration/__init__.py", line 191, in migrate_app
success = migrator.migrate_many(target, workplan, database)
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 221, in migrate_many
result = migrator.__class__.migrate_many(migrator, target, migrations, database)
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 292, in migrate_many
result = self.migrate(migration, database)
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 125, in migrate
result = self.run(migration)
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 99, in run
return self.run_migration(migration)
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 81, in run_migration
migration_function()
File "/app/lib/python2.7/site-packages/south/migration/migrators.py", line 57, in <lambda>
return (lambda: direction(orm))
File "/app/notecard/notecards/migrations/0003_initial.py", line 15, in forwards
('user', self.gf('django.db.models.fields.related.ForeignKey')(to=orm['auth.User'])),
File "/app/lib/python2.7/site-packages/south/db/generic.py", line 226, in create_table
', '.join([col for col in columns if col]),
File "/app/lib/python2.7/site-packages/south/db/generic.py", line 150, in execute
cursor.execute(sql, params)
File "/app/lib/python2.7/site-packages/django/db/backends/util.py", line 34, in execute
return self.cursor.execute(sql, params)
File "/app/lib/python2.7/site-packages/django/db/backends/postgresql_psycopg2/base.py", line 44, in execute
return self.cursor.execute(query, args)
django.db.utils.DatabaseError: relation "notecards_semester" already exists
我有3个型号。部分,学期和记录卡。我在Notecards模型中添加了一个字段,我无法在Heroku上添加它。
谢谢。
答案 0 :(得分:5)
您必须伪装创建表的迁移,然后照常运行其他迁移。
manage.py migrate app_name 000X --fake
manage.py migrate app_name
000X是您创建表格的迁移次数。
答案 1 :(得分:1)
首先,从0003_initial和0005_initial的外观来看,您已经完成了多个schemamigration myapp --initial
命令,这些命令添加了create_table语句。有两组这些肯定会导致问题,因为一个人将创建表,然后下一个将尝试创建现有表。
您的migrations
文件夹可能完全受到奇怪迁移的污染。
无论如何,虽然我理解在本地计算机和远程计算机上运行schemamigration
的理论,但这可能是您问题的根源。 Schemamigration生成一个新的迁移 - 如果您必须在开发服务器上运行它,提交它,推送它,然后在生产机器上生成另一个迁移,您可能最终会重叠迁移。
另一件事:如果您在远程计算机上运行syncdb并且它正在生成表,这意味着您的数据库是100%最新的 - 不需要迁移。您需要使用完整的migrate --fake
来匹配迁移到数据库。
I ran syncdb locally.
I ran manage.py schemamigration app_name locally
I ran manage.py migrate app_name --fake locally
I commit and pushed to heroku master
I ran syncdb on heroku
I ran manage.py schemamigration app_name on heroku
# if you ran syncdb, your DB would be in the final state.
I ran manage.py migrate app_name on heroku
# if you ran syncdb, your DB would be in the final state. Nothing to migrate.