Questions tagged [django-south]

Tool to provide consistent, easy-to-use and database-agnostic database migrations for Django applications. Deprecated since Django 1.7.

South was a tool to provide consistent, easy-to-use and database-agnostic s for applications.

Since Django 1.7, the features previously provided by South are included directly in Django.

1022 questions
27
votes
1 answer

South - How to force certain migration?

I have a migration, 003, that creates a new table, but for some reason, South isn't creating a new table after executing that migration: I am doing the following command: [kelp@web187 goals]$ python2.7 manage.py migrate main…
egidra
  • 8,537
  • 19
  • 62
  • 89
26
votes
2 answers

Manage.py : Unknown command: 'migrate'

I'm using django and I'm facing a little problem. I would like to use the 'migrate' command with manage.py But when I try I get this error message: Unknown command: 'migrate' Type 'manage.py help' for usage. I have south installed (I installed…
Marcolac
  • 901
  • 4
  • 14
  • 27
25
votes
1 answer

Upgrading from Django 1.6 (with south) to 1.8 doesn't modify 'last_login' on the user table

I have upgraded from Django 1.6.5 (with south migrations) to Django 1.8. I have followed the instructions here: https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south So, I remove South, delete my previous migrations and run…
LondonAppDev
  • 8,501
  • 8
  • 60
  • 87
25
votes
1 answer

Is there a Django 1.7+ replacement for South's add_introspection_rules()?

Back in the days of South migrations, if you wanted to create a custom model field that extended a Django field's functionality, you could tell South to use the introspection rules of the parent class like so: from south.modelsinspector import…
Troy
  • 21,172
  • 20
  • 74
  • 103
25
votes
8 answers

South migration error: NoMigrations exception for django.contrib.auth

I have been using South on my project for a while, but I recently did a huge amount of development and changed development machine and I think something messed up in the process. The project works fine, but I can't apply migrations. Whenever I try…
danpalmer
  • 2,163
  • 4
  • 24
  • 41
25
votes
4 answers

Migrating data from "Many-To-Many" to "Many-To-Many Through" in django

I've got a model class Category(models.Model): title = models.CharField(...) entry = models.ManyToManyField(Entry,null=True,blank=True, related_name='category_entries', …
Bryce
  • 8,313
  • 6
  • 55
  • 73
25
votes
3 answers

South + Django 1.4 Database error

I have just installed my Django project on a new system, and installed Django 1.4. However when I try to run manage.py runserver or manage.py syncdb I get this error from South: Validating models... Unhandled exception in thread started by
saul.shanabrook
  • 3,068
  • 3
  • 31
  • 49
23
votes
2 answers

What is a Django South GhostMigrations exception and how do you debug it?

Made some changes to my Django app's model and used South to migrate them on my development machine (migrations 0004 through 0009). But when trying to migrate these changes on the server, I get a "GhostMigrations" error. There isn't much good…
jchung
  • 903
  • 1
  • 11
  • 23
22
votes
7 answers

Is using multiple databases and South together possible?

My current project is getting extended with geographical stuff, so I'm trying to integrate GeoDjango and import some shapefiles for starters. My setup consists of the following: MySQL 5.0 as 'default' database, previously the only…
Nikolai Prokoschenko
  • 8,465
  • 11
  • 58
  • 97
22
votes
5 answers

how to restore dropped table with django-south?

I wanted to clear out a table in my DB, so I dropped the table. Normally I would do manage.py syncdb to re-create it. However, the answer here says not to use syncdb anymore. So, what do I do instead?
Claudiu
  • 224,032
  • 165
  • 485
  • 680
22
votes
6 answers

Database migrations on django production

From someone who has a django application in a non-trivial production environment, how do you handle database migrations? I know there is south, but it seems like that would miss quite a lot if anything substantial is involved. The other two…
David542
  • 104,438
  • 178
  • 489
  • 842
21
votes
2 answers

Django south migration - Adding FULLTEXT indexes

I need to add a FULLTEXT index to one of my Django model's fields and understand that there is no built in functionality to do this and that such an index must be added manually in mysql (our back end DB). I want this index to be created in every…
GeneralBecos
  • 2,476
  • 2
  • 22
  • 32
21
votes
4 answers

south migration: "database backend does not accept 0 as a value for AutoField" (mysql)

I'm new to django and trying to have a Foreign key back to users for an assignee and reporter. But when i'm trying to apply the change with South i get the error ValueError: The database backend does not accept 0 as a value for AutoField. My Model…
user968808
20
votes
4 answers

On Heroku, is there danger in a Django syncdb / South migrate after the instance has already restarted with changed model code?

On Heroku, as soon as you push new code, the web-serving instances restart... even if the underlying database schema additions/changes (via syncdb or south migrate) haven't yet been applied. In many cases, this might just cause harmless errors…
gojomo
  • 52,260
  • 14
  • 86
  • 115
20
votes
2 answers

Explicitly set MySQL table storage engine using South and Django

I'm running into an issue that South creates the DB table for a new model as INNODB when I migrate but creates the table as MYISAM when another developer runs their own migration. The problem with this is that all my other tables are MYISAM so using…
1 2
3
68 69