All migrations have been created from scratch using South==0.7.5 and saved as 0001_initial; others are empty just to keep migration history consistent. Thanks @Bouke for suggesting this approach.
This is just a first tentative.
Needs docs (pre 2.3.2 installation needs first to install and upgrade to 2.3.2 and then upgrade to this versione) and tests (automated syncdb / migrate on at least sqlite/pgsql/mysql as suggested by @digi604).
syncdb / migrate
Tested on a sample project both with and without CMS_MODERATOR on
Fixes #1427, but many other opened issues are related to migrations/south: maybe they should be referenced here to address those cases in this PR.
Migration related issues:
Migrations rewritten: all migrations has been created from scratch us…
…ing using South==0.7.5 and saved as 0001_initial; all others are empty just to keep migration history consistent
I think we should ask @andrewgodwin what he thinks about this approach. (Please apologize my rude pinging Andrew)
Looks alright to me - provided you make sure everyone has migrated to the most recent migrations in all apps before they pull these changes.
SOUTH_TESTS_MIGRATE = True
Yes sorry, currently quite busy.
I can work on it next week
Referencing some tickets: #1032
any updates here?
Merge pull request #1474 from ojii/simple-plugins
Saner defaults for plugins
Documentation for new migrations
I'm having some issues with multi-db tests.
There are many failing tests on postgres and mysql, some fails as they assume sqlite (e.g. query-counting test); fails differ from postgres to mysql.
Tests fail porting multi-db tests on current develop or using SOUTH_TESTS_MIGRATE = False , so it's not migrations related.
I'd skip multi-db in this PR, and create a new one to work on it separately
SOUTH_TESTS_MIGRATE = False
Merge branch 'feature/migrations_history_rewrite' of github.com:yakky…
…/django-cms into feature/migrations_history_rewrite
Pushed documentation changes,
Upmf, don't know why github took piquadrat commit too
Created new PR for multi-db testing.