diff options
author | Derek Prior <derekprior@gmail.com> | 2018-04-19 15:41:01 -0400 |
---|---|---|
committer | Derek Prior <derekprior@gmail.com> | 2018-04-24 11:18:11 -0400 |
commit | 84718df86097442f85999d6f2e6f6b8b59724c3f (patch) | |
tree | 0b5967db5a3e0e333e5bffd42f9f9f150071ab11 /activesupport/test/core_ext/module/concerning_test.rb | |
parent | fb9ed7b0dff7dcf8a00e42cd45ec645211c04afc (diff) | |
download | rails-84718df86097442f85999d6f2e6f6b8b59724c3f.tar.gz rails-84718df86097442f85999d6f2e6f6b8b59724c3f.tar.bz2 rails-84718df86097442f85999d6f2e6f6b8b59724c3f.zip |
Update schema.rb documentation [CI SKIP]
The documentation previously claimed that `db/schema.rb` was "the
authoritative source for your database schema" while simultaneously
also acknowledging that the file is generated. These two statements are
incongruous and the guides accurately call out that many database
constructs are unsupported by `schema.rb`. This change updates the
comment at the top of `schema.rb` to remove the assertion that the file
is authoritative.
The documentation also previously referred vaguely to "issues" when
re-running old migrations. This has been updated slightly to hint at the
types of problems that one can encounter with old migrations.
In sum, this change attempts to more accurately capture the pros, cons,
and shortcomings of the two schema formats in the guides and in the
comment at the top of `schema.rb`.
[Derek Prior & Sean Griffin]
Co-authored-by: Sean Griffin <sean@seantheprogrammer.com>
Diffstat (limited to 'activesupport/test/core_ext/module/concerning_test.rb')
0 files changed, 0 insertions, 0 deletions