I have noticed that when RAILS_ENV=development (which is the default when in development) rails db:drop and rails db:create tasks run on both the development, and test databases (drop, and create databases for both test and development environment). You can see this documented here . rails:db:migr…

Db:drop, create & migrate behavior with RAILS_ENV=development

taylorthurlow (Taylor Thurlow) May 8, 2020, 3:19am 2

I agree - this distinction has always been really unclear - I find myself assuming one case or another, and I’m usually wrong.

1 Like

Topic		Replies	Views
rake db:create (in development mode) creates development _and_ test database rubyonrails-talk	1	148	February 18, 2011
rake db:test:prepare rubyonrails-talk	2	111	April 4, 2012
Rake Bug? db:create:all directs db:migrate to the test db.. rubyonrails-talk	0	111	January 31, 2008
Difference with rake db:test:load and rake db:schema:load RAILS_ENV=test with stored procedures/methods rubyonrails-core	1	171	October 24, 2013
rake db:migrate should run for all environements rubyonrails-talk	3	132	February 19, 2009