Rails SQLite Dev and Test database are the same. Why?

Question

I inherited a Rails project where the (SQLite) Dev and Test databases are the same, as in the database.yml file.

Are there any advantages to this? Why would anyone do this?

iblue · Accepted Answer · 2012-08-01 22:54:06Z

2

The test database will get overwritten by the tests normally (unless you use transactional fixtures). If test and development databases are the same, your data will be erased every time you run your test suite. Development data may interfere with the test suite and make it unrealiable.

I would cleary consider this a design mistake. There is no reason, you should ever do this. Even the database.yml in a freshly created rails app states:

# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.

answered Aug 1, 2012 at 22:54

iblue

30.6k20 gold badges93 silver badges130 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Lym · Accepted Answer · 2012-08-01 23:00:20Z

1

There are no advantages to this. There are disdvantages. test and development or production databases are supposed to be different. A lot of people leave test and development settings the same and it's not that big of a problem since the most important one is the production database. That's the reason i can think of that made the previous dev. on the project do that. It should not be like that though.

answered Aug 1, 2012 at 23:00

Lym

3265 silver badges15 bronze badges

Collectives™ on Stack Overflow

Rails SQLite Dev and Test database are the same. Why?

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related