On Jul 26, 2010, at 12:36 PM, Bruno Cardoso wrote: > Thanks for the answers. > > What both solutions (from Ashley and David) do is not modify the BD in > anyway, so nothing gets dropped and nothing is created. This resolves > the problem but what if I want a clean installation in each test run?
So is your goal here to have the rake task(s) ignore the fact that you have pending migrations, but still have it reset the test database so it's schema looks like the development database schema? > Is > there a way to keep my "schema_migrations" table or remove the check for > migration scripts? I would still like to recreate the rest of the > tables. > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > rspec-users mailing list > rspec-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/rspec-users _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
