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? -- 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.
