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…

Thank you for bring this up. [image] markvanlan: Is there any reason why these commands interact with RAILS_ENV differently? If not, I would love to see db:migrate , migrate the test database as well, to save the step of running another command The test schema is automatically maintained …

Additionally in Docker environments where the database reasonably lives on mysql or some other non-localhost hostname the “This tool only operates on local databases” renders the database tools pretty well useless, or at least unreliable and unpredictable.

A vote from Twitter: [image] Samuel Williams @ioquatix @avdi @dhh You asked. Here is one I think needs a bit more attention. github.com/rails/rails/is… 1:47 PM - 8 May 2020 2 Referring to: https://github.com/rail…

[image] rafaelfranca: The test schema is automatically maintained by the Rails test framework ( bin/rails test command), so you don’t need to call db:migrate on the test database. I don’t know if it is also automatically maintained by RSpec. RSpec doesn’t do this by default, so for anyone usi…

maintain_test_schema! also is part of rspec-rails’s default rails_helper now, which is great.

I would prefer when all* the rails db:... commands would run by default only for one environment. The default is development, so I would expect them to only create or drop or migrate my development database. It is not only confusing that some commands change development and test while others don’t…

[image] Betsy_Haibel: maintain_test_schema! also is part of rspec-rails 's default rails_helper now, which is great. Does this mean what I was asking for in the OP is now done?

Not quite! This isn’t baked into Rails now or anything. I meant that if you run bin/rails generate rspec:install, then the generated rails_helper.rb includes code that should run the equivalent of db:test:prepare at the start of every test run.

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

A May Of WTFs

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.

Topic		Replies	Views
rake db:create (in development mode) creates development _and_ test database rubyonrails-talk	1	164	February 18, 2011
Merge db:migrate + db:test:prepare rubyonrails-core	30	611	September 24, 2010
Rake Bug? db:create:all directs db:migrate to the test db.. rubyonrails-talk	0	137	January 31, 2008
"rake test" wipes my development database rubyonrails-talk	1	179	August 3, 2008
rake db:migrate should run for all environements rubyonrails-talk	3	182	February 19, 2009

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

Related topics

More Resources