Closed andyw8 closed 4 months ago
The first time someone cloned and runs the tests, they'll get a confusing error because the dB doesn't yet exist.
I originally considered checking if the DB exists first, but creating is very quick so I don't think that's necessary.
(for sqlite3 at least, db:setup is idempotent so there's no problem with it being re-run. We don't care about the data in the DB).
db:setup
The first time someone cloned and runs the tests, they'll get a confusing error because the dB doesn't yet exist.
I originally considered checking if the DB exists first, but creating is very quick so I don't think that's necessary.
(for sqlite3 at least,
db:setupis idempotent so there's no problem with it being re-run. We don't care about the data in the DB).