On 13 August 2010 00:08, Fearless Fool <li...@ruby-forum.com> wrote: > Short form: How can I convince migrate to create or modify tables in a > database other than the "current" one? In other words, how can I get > migrate to honor establish_connection :external in a model definition? > > Details: I have a large "almost static" dataset that never changes as a > result of my Rails app, so it's residing in a separate database. (It > gets refreshed nightly with external data.) I'd like to maintain its > schema using the Rails migration mechanism, but despite my efforts, > migrate only updates tables for the current environment (e.g. > _development or _test).
All this hassle makes one wonder whether it might be possible to combine the two databases into one. That would make life a lot simpler, if it were possible. Colin -- 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.
