Thursday, July 23, 2015
Hi every one!
-- In rails every evolution of a model must be executed through migrations, isn't it?
And if it must be done this way, how can we control migrations in a production deployment?
We have to take care of our data during the migrations in order to don't erase anything.
What is the best way to do this?
Thank you so much in advance.
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/a5bbcaa7-5689-4440-978b-bd47f3f15488%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment