Remove deprecation warning during migrate about timestamps #242
Conversation
This file contains 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
This warning occurs when you tried to rake:db migrate in a rails 4.2 application. It's a deprecation warning for upcoming rails 5, a null option need to be given : DEPRECATION WARNING: `#timestamp` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing. (called from block in up at db/migrate/20151104181305_create_activities.rb:12)
|
Sweet, thanks Julien! |
pokonski
added a commit
that referenced
this pull request
Dec 3, 2015
…ning Remove deprecation warning during migrate about timestamps
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.
This warning occurs when you tried to rake:db migrate in a rails 4.2
application. It's a deprecation warning for upcoming rails 5, a null
option need to be given :
DEPRECATION WARNING:
#timestampwas called without specifying anoption for
null. In Rails 5, this behavior will change tonull: false. You should manually specifynull: trueto prevent the behaviorof your existing migrations from changing. (called from block in up at
db/migrate/20151104181305_create_activities.rb:12)