diff options
| author | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2014-05-16 13:11:33 -0300 |
|---|---|---|
| committer | Rafael Mendonça França <rafaelmfranca@gmail.com> | 2014-05-16 13:11:33 -0300 |
| commit | f3de18278e48097442101734cde1711d3dd6e6df (patch) | |
| tree | aca5366628d11639d655093c5bedcc4a0ccece6c | |
| parent | f7552e50efc01c6e3a97a3e5b2b54478f7f7a6ab (diff) | |
| parent | b48bc869fa55a1b4622ca316a9b62b6da901402f (diff) | |
| download | rails-f3de18278e48097442101734cde1711d3dd6e6df.tar.gz rails-f3de18278e48097442101734cde1711d3dd6e6df.tar.bz2 rails-f3de18278e48097442101734cde1711d3dd6e6df.zip | |
Merge pull request #15113 from leafac/document-schema-conflicts
Document conflicts in `db/schema.rb` [ci skip]
| -rw-r--r-- | guides/source/migrations.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/guides/source/migrations.md b/guides/source/migrations.md index c61ccfe94a..fe1a6a4697 100644 --- a/guides/source/migrations.md +++ b/guides/source/migrations.md @@ -902,6 +902,11 @@ schema into a RDBMS other than the one used to create it. Because schema dumps are the authoritative source for your database schema, it is strongly recommended that you check them into source control. +`db/schema.rb` contains the current version number of the database. This +ensures conflicts are going to happen in the case of a merge where both +branches touched the schema. When that happens, solve conflicts manually, +keeping the highest version number of the two. + Active Record and Referential Integrity --------------------------------------- |