github/rails
1
1
Fork 0
mirror of https://github.com/github/rails.git synced 2026-04-26 03:00:59 -04:00
Code Issues Packages Projects Releases Wiki Activity

Correct formatting

Browse Source
This commit is contained in:
mhutchin
2011-10-07 08:26:05 -07:00
parent d4ea804e21
commit fca2613ec4
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
railties/guides/source/migrations.textile
View File

@@ -628,11 +628,7 @@ There is no need (and it is error prone) to deploy a new instance of an app by r
For example, this is how the test database is created: the current development database is dumped (either to +db/schema.rb+ or +db/development.sql+) and then loaded into the test database.
Schema files are also useful if you want a quick look at what attributes an Active Record object has. This information is not in the model's code and is
frequently spread across several migrations, but is summed up in the schema
file. The "annotate_models":http://github.com/ctran/annotate_models
gem automatically adds and updates comments at the top of each model summarizing
the schema if you desire that functionality.
Schema files are also useful if you want a quick look at what attributes an Active Record object has. This information is not in the model's code and is frequently spread across several migrations, but is summed up in the schema file. The "annotate_models":http://github.com/ctran/annotate_models gem automatically adds and updates comments at the top of each model summarizing the schema if you desire that functionality.
h4. Types of Schema Dumps