> The normal workflow would be to (1) migrate your development database, > (2) prepare your test database (rake db:test:prepare), (3) run your > tests, and finally (4) migrate your production/staging database as part > of your deployment process/script.
For f*!k sake!!! I just wasted 2 hours banging my head on the table, I had forgotten to do RAILS_ENV=test rake db:migrate!!! How in heck can people say that the migration of test_db and dev_db have to be kept separate? These 2 DBs must be in sync (tables, columns) at all time. -- 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-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 -~----------~----~----~----~------~----~------~--~---
