aboutsummaryrefslogtreecommitdiffstats
path: root/railties
diff options
context:
space:
mode:
authorVijay Dev <vijaydev.cse@gmail.com>2011-08-14 20:15:51 +0530
committerVijay Dev <vijaydev.cse@gmail.com>2011-08-14 20:15:51 +0530
commitac4dc5e240242ed53885e4cac7b48dd93773a329 (patch)
tree85551acb47ba7e581e151b4f30c705dec5fe9eef /railties
parent3c5715575d85e0df69f84357769fc4696fdec3da (diff)
downloadrails-ac4dc5e240242ed53885e4cac7b48dd93773a329.tar.gz
rails-ac4dc5e240242ed53885e4cac7b48dd93773a329.tar.bz2
rails-ac4dc5e240242ed53885e4cac7b48dd93773a329.zip
rephrase how the verbose methods in a migration work
Diffstat (limited to 'railties')
-rw-r--r--railties/guides/source/migrations.textile6
1 files changed, 3 insertions, 3 deletions
diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile
index 4476e067a6..9da12e2e18 100644
--- a/railties/guides/source/migrations.textile
+++ b/railties/guides/source/migrations.textile
@@ -471,8 +471,8 @@ By default migrations tell you exactly what they're doing and how long it took.
Several methods are provided that allow you to control all this:
-* +suppress_messages+ suppresses any output generated by its block
-* +say+ outputs text (the second argument controls whether it is indented or not)
+* +suppress_messages+ takes a block as an argument and suppresses any output generated by the block.
+* +say+ takes a message argument and outputs it as is. A second boolean argument can be passed to specify whether to indent or not.
* +say_with_time+ outputs text along with how long it took to run its block. If the block returns an integer it assumes it is the number of rows affected.
For example, this migration
@@ -510,7 +510,7 @@ generates the following output
20080906170109 CreateProducts: migrated (10.0097s)
</shell>
-If you just want Active Record to shut up then running +rake db:migrate VERBOSE=false+ will suppress any output.
+If you just want Active Record to shut up then running +rake db:migrate VERBOSE=false+ will suppress all output.
h3. Using Models in Your Migrations