Colin Law wrote: > On 13 August 2010 18:05, Fearless Fool <li...@ruby-forum.com> wrote: >> schema.rb. �Given that, it doesn't have enough information to know which >> external database, but that shouldn't really matter. > I suppose you could test RAILS_ENV in the migration rb file and only > do the migration if it is appropriate for the env specified. Then > rake db:migrate RAILS_ENV=development > would apply relevant migrations to the development db > rake db:migrate RAILS_ENV=external > would apply relevant migrations to the external db. >
I seem also to recall some talk of using establish_connection in the migration files themselves. Will that work, or am I misremembering? > Colin Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- 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-t...@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.
