Use dynamic settings in migrations to match model - #217
Merged
brosner merged 1 commit intoJul 21, 2016
Conversation
…Django migration autodetector from making new migrations when a user changes settings.
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
3 participants
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.
Currently, if the user changes his
ACCOUNT_LANGUAGESsetting the Django migration autodetector will create new migrations inside of django-user-accounts because the value ofAccount.language.choiceshas changed. This pull request fixes that by also referencing settings within the migration.This seems to be the best practice and is used by django-cms migrations and discussed in a Django ticket.