First time here? Check out the FAQ!

Revision history  [back]

edit I believe these issues were fixed now - please check new code from the repository.

With the python manage.py syncdb --all use command python manage.py migrate --fake and you should avoid these issues. Is there specific reason why you cannot use Postgresql?

syncdb --all is a version of syncdb command that is provided by the Django South app. The --all option will force creation of all tables to the spec provided by the models module. migrate --fake will mark all database migrations as applied without actually running any migration code.

edit I believe these issues were fixed now - please check new code from the repository.

With the python manage.py syncdb --all use command python manage.py migrate --fake and you should avoid these issues. Is there specific reason why you cannot use Postgresql?

syncdb --all is a version of syncdb command that is provided by the Django South app. The --all option will force creation of all tables to the spec provided by the models module. migrate --fake will mark all database migrations as applied without actually running any migration code.

With the python manage.py syncdb sync --all use command python manage.py migrate --fake and you should avoid these issues. Is there specific reason why you cannot use Postgresql?

syncdb --all is a version of syncdb command that is provided by the Django South app. The --all option will force creation of all tables to the spec provided by the models module. migrate --fake will mark all database migrations as applied without actually running any migration code.