On 30 January 2015 at 14:17, Sean Kelley <kelleyfarm@gmail.com> 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+unsubscribe@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/CAL%3D0gLv6EcQTK5NxL7-1_mp-rKkNGeoLbV65cVB5RkW%3D2PMVFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment