django-south

I've run into the same issue presented by the commenter here: Django South - table already exists There was no follow-up, so I thought I'd post a new question. I have a Django app whose migrations I manage with South. I added a field to my model then ran ./manage schemamigration my_app --auto which ran as expected. Running ./manage migrate my_app however, resulted in an error indicating that the table associated with the model I changed already exists. This led me to the above linked question, so running ./manage migrate my_app --fake resolved the table error, but now I'm getting a Django

Ok, so this seems like a really silly thing to ask, and I'm sure I'm missing something somewhere. How do you perform a backwards migration using South on Django? So I've tweaked my models, created a migration with schemamigration , run the migration with migrate , and now I realise that's not quite what I wanted and I want it back the way before. Short of manually editing db tables and removing migration files, how should I go about rolling the migration back? I find references to backward migrations using South via Google, but have yet to find a solid code example for it. Can anyone help? You

I was wondering if the following migration is possible with Django south and still retain data. Before: I currently have two apps, one called tv, one called movies, each with a VideoFile model (simplified here): tv/models.py: class VideoFile(models.Model): show = models.ForeignKey(Show, blank=True, null=True) name = models.CharField(max_length=1024, blank=True) size = models.IntegerField(blank=True, null=True) ctime = models.DateTimeField(blank=True, null=True) movies/models.py: class VideoFile(models.Model): movie = models.ForeignKey(Movie, blank=True, null=True) name = models.CharField(max

First, I create my database. create database mydb; I add "south" to installed Apps. Then, I go to this tutorial: http://south.aeracode.org/docs/tutorial/part1.html The tutorial tells me to do this: $ py manage.py schemamigration wall --initial >>> Created 0001_initial.py. You can now apply this migration with: ./manage.py migrate wall Great, now I migrate. $ py manage.py migrate wall But it gives me this error... django.db.utils.DatabaseError: (1146, "Table 'fable.south_migrationhistory' doesn't exist") So I use Google (which never works. hence my 870 questions asked on Stackoverflow), and I

(I know there is a title the same as this, but the question is different). I have managed to get my development machine migrations and production migrations out of sync. I have a Django app which was using South. I had my own workflow that worked fine (it probably wasn't the correct way to do things, but I had no problems with it). Basically I have a script that copies the production database dump to my development machine. It also copied the migration files. That way the two were in synch, and I could run South commands as normal. Now I have upgraded to 1.7, and started using migrations. When

I am trying to apply a migration but am getting the error: django.db.utils.OperationalError: (1050, "Table 'customers_customer' already exists") I get this by issuing the following command: python manage.py migrate My customer table already exists, so what do I do to let the migration know this, not error out, and run my modification to my model? I ran this on my local environment with local database with no problem. It is when I pointed my database to production and ran migrate above that I get this error. If you have the table created in the database, you can run python manage.py migrate -

I am trying to get started with South. I had an existing database and I added South ( syncdb , schemamigration --initial ). Then, I updated models.py to add a field and ran ./manage.py schemamigration myapp --auto . It seemed to find the field and said I could apply this with ./manage.py migrate myapp . But, doing that gave the error: django.db.utils.DatabaseError: table "myapp_tablename" already exists tablename is the first table listed in models.py . I am running Django 1.2, South 0.7 Ashok since you already have the tables created in the database, you just need to run the initial migration