Added Django 1.7 migrations#318
Merged
omab merged 1 commit intoomab:masterfrom Jul 7, 2014
ondrowan:master
Merged
Conversation
Author
|
Coincidentally, South 1.0 was released today. |
Owner
|
Thanks! Regarding South migrations, they should be added to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've added initial migration that's required in Django 1.7. I've tried it with most recent RC and it works well. The only problem is that social-auth hadn't used South migrations before and new folder
migrationsis backwards incompatible for users that still use South. AFAIK the only solution should be to create South migrations folder (eg.south_migrations) and tell users to use following setting:Or possibly the other way around. Rename this new folder to
django_migrationsand create newmigrationsfolder with South migrations. But that seems to be more complicated option.Feedback is welcome as I'm not 100% sure how to handle this situation.
Related to #270.