diff options
author | Alexander Sulfrian <alexander.sulfrian@fu-berlin.de> | 2015-09-17 16:23:53 +0200 |
---|---|---|
committer | Alexander Sulfrian <alexander.sulfrian@fu-berlin.de> | 2015-09-23 19:29:00 +0200 |
commit | eae3cfb904c86f519d409724585eafcab99c74bd (patch) | |
tree | 5cc1f70748ac002346960b1c41dc70d2432cadec /schemas/pathentry.xsd | |
parent | c3f00276aba871f7809f202d5fff95564a9e7309 (diff) | |
download | bcfg2-eae3cfb904c86f519d409724585eafcab99c74bd.tar.gz bcfg2-eae3cfb904c86f519d409724585eafcab99c74bd.tar.bz2 bcfg2-eae3cfb904c86f519d409724585eafcab99c74bd.zip |
DBSettings: Automatically upgrade migrations from south to django
On the first use with django-1.7 we manually get the south migration status
and fake apply the django migration to that point. With that users can switch
to django migrations at any point of time.
The code simply takes the name of the last south migration and forwards the
django migrations to that point. Therefor it is required to keep the names
of the migrations in sync.
It is required to keep the migration names of the two systems in sync.
Diffstat (limited to 'schemas/pathentry.xsd')
0 files changed, 0 insertions, 0 deletions