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 builtins. 

BR

Marcin

On Thursday, April 23, 2015 at 9:18:35 PM UTC+2, Rick Weinberger wrote:

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 documentation on the issue (closest I can find assumes I used to use South, which I did not) and searches for others with similar issues never seems to find my exact case.  Does anyone know where I can at least look for more information, if not how to fix it outright?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/65ccebac-d424-45b9-8c2c-ea420f58e052%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.