On 13 August 2010 21:40, Fearless Fool <[email protected]> wrote: > Colin Law wrote: >> A good point, but I think it would be ok. If you test the env inside >> the migration class, so that for the 'wrong' db it just appears like a >> do-nothing migration, then I think the fact that the migration has >> been run should be recorded as normal and all should be well. If that >> makes sense. >> >> Colin > > I like it, but wouldn't rake db:migrate generate a radically different > schema.rb depending on which RAILS_ENV I specify? Or would that not be > a problem?
Good point, I am well outside my comfort zone here. Googling for rails migration multiple databases produces a few links that might be useful. 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
