On 22-jul-2008, at 6:43, Teedub wrote:
Thanks
rake db:test:prepare did the trick. I am still a bit confused as to
why rake cares about a database that it isn't using.
But I guess that will all fall into place in my brain one day.
Well, the test database is for ehrm, testing :). So rake is actually
using it.
gr,
bartz
On Jul 21, 1:01 am, Rahoul Baruah <[EMAIL PROTECTED]> wrote:
On 21 Jul 2008, at 08:27, David Salgado wrote:
If you have created it, then perhaps the test db doesn't have the
right tables. So, try "rake db:test:prepare". You'll need to do that
after every migration as well.
Once your test database is built, using "rake spec" should ensure
that your test database matches the structure of your dev database,
before running your specifications.
Baz.
Rahoul Baruah
Web design and development:http://www.3hv.co.uk/
Serious Rails Hosting:http://www.brightbox.co.uk/
_______________________________________________
rspec-users mailing list
[EMAIL PROTECTED]://rubyforge.org/mailman/listinfo/
rspec-users
_______________________________________________
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
