Marco Antonio Filho wrote in post #991464: > Now comes the problem. I need to deploy these > changes > in the production servers. I already have the script to update the > changes, > but I don't know what is the conventional place to put it. Not in the > migrations, I know.
Why not a migration? Seems like the correct place for a one-shot change. Create the new table. Migrate the data. Once and done. I've done this numerous times on a project as the design evolves (create new table(s), reorganize existing data), and the migrations provide the audit trail of the actions. Just make sure your down action undoes everything appropriately, but that's what your dev environment is for, isn't it? -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
