Re: Django Migrations - Relation Already Exists

I'm not a newbie. Just avoid Django (South) migrations and syncdb. My advice - generate complete SQL for your project (based on migrations or sql and sqlindexes commands), move changes to reliable tool (i.e. Liquibase) as an initial migration, tune changesets if needed, and forget about builtin

Re: Django Migrations - Relation Already Exists

I'm a newbie here so be careful. I believe you can use manage.py migrate --fake That works for me. Johnf On 04/23/2015 11:37 AM, Rick Weinberger wrote: I posted the same question on stack overflow, here: http://stackoverflow.com/questions/29830928/django-db-utils-programmingerror-relation-alrea

Django Migrations - Relation Already Exists

I posted the same question on stack overflow, here: http://stackoverflow.com/questions/29830928/django-db-utils-programmingerror-relation-already-exists I basically can't figure out how to get my app to migrate, and I can't use syncdb, because I inherit from contrib.auth. I also can't find any