kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Clarify "Old Migrations" in "Active Record Migrations" guide [ci skip]

Browse source 
- Name rails app' files relatively to its root
  - `structure.sql` =>  `db/structure.sql`
  - `schema.rb` =>  `db/schema.rb`
- Clarify rails commands
  - `db:migrate` => `rails db:migrate`
  - `db:migrate:status` => `rails db:migrate:status`
- Add `/` to the end of `db/migrate` in order to express that it is
  directory and to keep consistency with `db/migrate/` above.

Follow up #33474
This commit is contained in:
bogdanvlviv 2018-08-12 15:08:07 +03:00
parent e3ae53f92c
commit e1817f80b4
No known key found for this signature in database
GPG key ID: E4ACD76A6DB6DFDD
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
guides/source/active_record_migrations.md
View file

@ -1050,17 +1050,17 @@ application.
Old Migrations
--------------
The `schema.rb` or `structure.sql` is a snapshot of the current state of your
The `db/schema.rb` or `db/structure.sql` is a snapshot of the current state of your
database and is the authoritative source for rebuilding that database. This
makes it possible to delete old migration files.
When you delete migration files in the `db/migrate/` directory, any environment
where `db:migrate` was run when those files still existed will hold a reference
where `rails db:migrate` was run when those files still existed will hold a reference
to the migration timestamp specific to them inside an internal Rails database
table named `schema_migrations`. This table is used to keep track of whether
migrations have been executed in a specific environment.
If you run the `db:migrate:status` command, which displays the status
If you run the `rails db:migrate:status` command, which displays the status
(up or down) of each migration, you should see `********** NO FILE **********`
displayed next to any deleted migration file which was once executed on a
specific environment but can no longer be found in the `db/migrate` directory.
specific environment but can no longer be found in the `db/migrate/` directory.