Ruby on Rails Wednesday, July 6, 2016


On Thursday, July 7, 2016 at 2:02:01 PM UTC+9, Douglas Teoh wrote:
I am in the process of upgrading an app to Rails 5. One thing that I stumbled on while recreating my test database was the `db:environment:set` command.

From what I can see, this makes a table named `internal_metadata` and stores an environment value.

Is running this command on all existing databases required? I cannot find any further information about this command in the upgrade guide or the ActiveRecord changelog notes.


Looks like this is for preventing accidental destruction of the production DB:

http://blog.bigbinary.com/2016/06/07/rails-5-prevents-destructive-action-on-production-db.html

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/f35cfaa9-cb12-42d1-861e-539f9d85e963%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment