HINT: Django 1.6 changed the default value of BooleanField from False… #128
Conversation
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
… to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.
Contributor
|
Thanks for the PR. Don't you think it's better to use a NullBooleanField [1]? |
Author
|
Hmm that might work but I think that's probably a larger change than just the default, probably a migration involved as well if the field isn't already set up to allow null values. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
… to None. See https://docs.djangoproject.com/en/1.6/ref/models/fields/#booleanfield for more information.