`rake db:drop db:create db:migrate` not run migrations in rails 8

[nleo]

As solo developer, when I start new project, I never know what exacly database schema will be.

Sometimes I edit recent or old migrations and want to rerun all with command: rake db:drop db:create db:migrate. Now seems this behavior is broken and rake db:migrate load schema, not run migrations as it expected by it's name. But there is another command: rake db:schema:load and it looks like confusing behavior.

[flavorjones]

Duplicate of #53832

[nleo]

@flavorjones I'm not sure. It's on PostgreSQL. And dev db creates with schema from schema.rb. If delete schema rb it runs migraiotns

$ rails db:drop db:create db:migrate
Dropped database 'app_development'
Dropped database 'app_test'
Created database 'app_development'
Created database 'app_test'
$

$ rm db/schema.rb; rails db:drop db:create db:migrate
Dropped database 'app_development'
Dropped database 'app_test'
Created database 'app_development'
Created database 'app_test'
== 20250103092742 DeviseCreateUsers: migrating ================================
-- create_table(:users)
   -> 0.0123s
....
$

seems different issues for me. but test db is empty for me too

$ psql app_test 
psql (15.3 (Ubuntu 15.3-1.pgdg18.04+1))
Type "help" for help.

app_test=# \d
Did not find any relations.
app_test=# 

but it not issue for me

[flavorjones]

Oh, interesting, I had assumed this was with SQLite, sorry about that.

[flavorjones]

Maybe related to ecbdfbc / #53320?

[jaspervanbrian]

@nleo are you using a secondary database? I'm noticing some oddities on db commands and have participated discussions on some database issues. I think this is maybe related to #52829

[nleo]

One database. Today generated app rails new myapp --database postgresql --skip-kamal --skip-solid --skip-jbuilder --css bootstrap -T

[mackuba]

@nleo they've changed the behavior of db:migrate in 8.0, that on a fresh database it now just loads the schema instead of running all migrations… see #53899.

If you want the previous behavior, you need to run db:migrate:reset to initialize a database, or alternatively override the db:migrate task to do something like before - this seems to work for me:

namespace :db do
  Rake::Task["db:migrate"].clear

  desc "Migrate the database (options: VERSION=x, VERBOSE=false, SCOPE=blog)."
  task :migrate => :load_config do
    ActiveRecord::Tasks::DatabaseTasks.migrate(skip_initialize: true)
    Rake::Task["db:_dump"].invoke
  end
end

[Frexuz]

db:migrate:reset drops my solid_queue tables (schema)? 🤔

is there another command to avoid this? or is this a bug i should create a new issue for?

[skipkayhil]

db:migrate:reset drops my solid_queue tables (schema)? 🤔

is there another command to avoid this? or is this a bug i should create a new issue for?

If you already have a schema, why do you need to db:migrate:reset instead of db:migrate?

[Frexuz]

If you already have a schema, why do you need to db:migrate:reset instead of db:migrate?

still in development mode, im changing existing migrations and reset the entire db