From e3ae53f92ca4b5349b7ca54e814063299de03bf0 Mon Sep 17 00:00:00 2001 From: bogdanvlviv Date: Sun, 12 Aug 2018 14:56:23 +0300 Subject: Clarify note that SQLite3 adapter doesn't support `add_foreign_key` [ci skip] Context https://github.com/rails/rails/pull/33563#discussion_r208891486. Follow up #33563 --- guides/source/active_record_migrations.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'guides/source') diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md index e2359a35f1..9446441b20 100644 --- a/guides/source/active_record_migrations.md +++ b/guides/source/active_record_migrations.md @@ -491,9 +491,8 @@ NOTE: Active Record only supports single column foreign keys. `execute` and `structure.sql` are required to use composite foreign keys. See [Schema Dumping and You](#schema-dumping-and-you). -NOTE: At this time, only the mysql, mysql2 and postgresql adapters support -foreign keys. Implementation for sqlite3 is partial, keys are created for new -tables but not for existing tables via `ALTER TABLE` statement. +NOTE: The SQLite3 adapter doesn't support `add_foreign_key` since SQLite supports +only [a limited subset of ALTER TABLE](https://www.sqlite.org/lang_altertable.html). Removing a foreign key is easy as well: -- cgit v1.2.3 From e1817f80b4a43ffda93c152d7bc260447e0610d6 Mon Sep 17 00:00:00 2001 From: bogdanvlviv Date: Sun, 12 Aug 2018 15:08:07 +0300 Subject: Clarify "Old Migrations" in "Active Record Migrations" guide [ci skip] - 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 --- guides/source/active_record_migrations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'guides/source') diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md index 9446441b20..4d195988f8 100644 --- a/guides/source/active_record_migrations.md +++ b/guides/source/active_record_migrations.md @@ -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. -- cgit v1.2.3