On Thu, Apr 7, 2011 at 4:02 PM, Ar Chron <li...@ruby-forum.com> wrote:
> 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 do agree with you. But I read so many articles that state that the migrations are supposed only to contain the structure of the tables, not changes in the records. I think I will stick with the migration then. It seems the best place to put these scripts for now. -- 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.
