The message I keep getting is that one of my tables already exists.
It's the first one in my schema. I noticed that some of my tests have
trouble between runs when it goes to drop certain tables, and it says
there's data or foreign key problems. I fgured that was the order of
the fixtures, but I don't know. How does Rails know the order to drop
things in so you don't get foreign key constraint issues?
Well, I'm not entirely sure this is correct, but I *believe* that it
works by deleting all the tables, then cloning the development database.
Yeah, digging through the rake tasks confirms this; the test task
(through a few steps of prereqs) calles db:test:purge.
How can I debug this? Is there a rake tasks that lets me drop my
database? Is it user permissions? I'm logging in as root.
db:test:purge will empty your test database.
Don't log in as root Set up new users for your databases.
What database engine are you using? Is your test database different
from your production/development databases?