This is what I got when I ran both commands
rails db:migrate:reset
$ rails db:migrate:reset
Dropped database 'db/development.sqlite3'
Dropped database 'db/test.sqlite3'
Created database 'db/development.sqlite3'
Created database 'db/test.sqlite3'
== 20190824101540 CreateUsers: migrating ======================================
-- create_table(:users)
-> 0.0005s
== 20190824101540 CreateUsers: migrated (0.0005s) =============================
== 20190825083402 AddIndexToUsersEmail: migrating =============================
-- add_index(:users, :email, {:unique=>true})
-> 0.0005s
== 20190825083402 AddIndexToUsersEmail: migrated (0.0006s) ====================
== 20190825085927 AddPasswordDigestToUsers: migrating =========================
-- add_column(:users, :password_digest, :string)
-> 0.0006s
== 20190825085927 AddPasswordDigestToUsers: migrated (0.0006s) ================
rails db:reset
$ rails db:reset
Dropped database 'db/development.sqlite3'
Dropped database 'db/test.sqlite3'
Created database 'db/development.sqlite3'
Created database 'db/test.sqlite3'
-- create_table("users", {:force=>:cascade})
-> 0.2180s
-- create_table("users", {:force=>:cascade})
-> 0.1696s
Looks like rake db:migrate:reset
and rake db:reset
does the same things except the fact that rake db:migrate:reset
also displays the migration log.
Is there any difference between the two? Or is one just an alias for the other?