If I run: bundle exec rake db:drop db:create db:migrate I get error that db:migrate needs to be run with RAILS_ENV=test if I bundle exec rake db:drop db:create db:migrate RAILS_ENV=test I get error regarding duplicate table again
If I delete db from postgres management screen then run bundle exec rake db:drop db:create db:migrate RAILS_ENV=test I can again run the test once, but the second time I get the error that migrations are pending and to run db:migrate RAILS_ENV=test I wonder why the act of running a simple test trigges this migration message On Friday, January 30, 2015 at 9:41:26 AM UTC-5, Colin Law wrote: > > On 30 January 2015 at 14:17, Sean Kelley <kelle...@gmail.com <javascript:>> > wrote: > > > > Thanks. Your command line affects development db also which is not > ideal. I looked up db:test:prepare and it appears to be deprecated in 4.2 > > > http://stackoverflow.com/questions/15169894/what-does-rake-dbtestprepare-actually-do > > > > > I decided to try it anyway with RAILS_ENV=test but I get same error of > duplicate table 'users' so I tried without the test env set and I get db > connection is closed message for test. > > I presume your development db is up to date (so running migrate on > that does nothing). > What happens if you recreate the test db and then run migrate on it? > Does the migrate run successfully? > > Colin > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/2f7150cc-6139-4387-83a7-7ec254d5a309%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
