diff options
author | Xavier Noria <fxn@hashref.com> | 2009-05-04 20:56:59 +0200 |
---|---|---|
committer | Xavier Noria <fxn@hashref.com> | 2009-05-04 20:57:29 +0200 |
commit | 912da7fb98cfdabe68477db146eaf25bb98f0f7e (patch) | |
tree | aabc32db048f421588f6be32be45889e8eab1a51 | |
parent | 13b4a9e8d7b3d8335ba96a5b408ee8e7a310bafc (diff) | |
download | rails-912da7fb98cfdabe68477db146eaf25bb98f0f7e.tar.gz rails-912da7fb98cfdabe68477db146eaf25bb98f0f7e.tar.bz2 rails-912da7fb98cfdabe68477db146eaf25bb98f0f7e.zip |
tray and -> try to, thanks to FelixLeiter
-rw-r--r-- | railties/guides/source/migrations.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/migrations.textile b/railties/guides/source/migrations.textile index bcea5e0cb5..c408e25e61 100644 --- a/railties/guides/source/migrations.textile +++ b/railties/guides/source/migrations.textile @@ -508,7 +508,7 @@ The migration has its own minimal copy of the +Product+ model and no longer care h4. Dealing with Changing Models -For performance reasons information about the columns a model has is cached. For example if you add a column to a table and then try and use the corresponding model to insert a new row it may try and use the old column information. You can force Active Record to re-read the column information with the +reset_column_information+ method, for example +For performance reasons information about the columns a model has is cached. For example if you add a column to a table and then try and use the corresponding model to insert a new row it may try to use the old column information. You can force Active Record to re-read the column information with the +reset_column_information+ method, for example <ruby> class AddPartNumberToProducts < ActiveRecord::Migration |