aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorvishalzambre <v.zambre@gmail.com>2017-04-19 11:31:00 +0530
committervishalzambre <v.zambre@gmail.com>2017-04-19 11:31:00 +0530
commite2648c42abe7466e2c982db6c5fd4565a0555562 (patch)
tree717ea3bdd5197dae9a09c44c6846bdae14254518
parentdc107956c933269d652cb8d283cf071bdbdb2066 (diff)
downloadrails-e2648c42abe7466e2c982db6c5fd4565a0555562.tar.gz
rails-e2648c42abe7466e2c982db6c5fd4565a0555562.tar.bz2
rails-e2648c42abe7466e2c982db6c5fd4565a0555562.zip
[ci skip] Changed plain text to NOTE.
-rw-r--r--guides/source/active_record_migrations.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/guides/source/active_record_migrations.md b/guides/source/active_record_migrations.md
index 6e7e29ed60..75e1096426 100644
--- a/guides/source/active_record_migrations.md
+++ b/guides/source/active_record_migrations.md
@@ -972,11 +972,11 @@ on. Because this is database-independent, it could be loaded into any database
that Active Record supports. This could be very useful if you were to
distribute an application that is able to run against multiple databases.
-There is however a trade-off: `db/schema.rb` cannot express database specific
-items such as triggers, stored procedures or check constraints. While in a
-migration you can execute custom SQL statements, the schema dumper cannot
-reconstitute those statements from the database. If you are using features like
-this, then you should set the schema format to `:sql`.
+NOTE: `db/schema.rb` cannot express database specific items such as triggers,
+sequences, stored procedures or check constraints, etc. While in a migration you
+can execute custom SQL statements, the schema dumper cannot reconstitute those
+statements from the database. If you are using features like this, then you
+should set the schema format to `:sql`.
Instead of using Active Record's schema dumper, the database's structure will
be dumped using a tool specific to the database (via the `db:structure:dump`