diff options
| author | Katrina Owen <katrina.owen@gmail.com> | 2012-07-13 22:48:32 +0200 |
|---|---|---|
| committer | Katrina Owen <katrina.owen@gmail.com> | 2012-10-10 23:44:43 +0200 |
| commit | a1d2f693776952e1f6ca7b347919047dbb4617f2 (patch) | |
| tree | 14d2f0e07031e325110e933acc3965708b83e5ab /actionpack/lib/action_view/model_naming.rb | |
| parent | ecf460e7c40e7a38b6a548261e8d052849f3b313 (diff) | |
| download | rails-a1d2f693776952e1f6ca7b347919047dbb4617f2.tar.gz rails-a1d2f693776952e1f6ca7b347919047dbb4617f2.tar.bz2 rails-a1d2f693776952e1f6ca7b347919047dbb4617f2.zip | |
Expand caveat about models in migrations (rails guide)
This is an attempt to address issue #6939, where an earlier migration
added a column to the database, and a later migration uses a model and
references that column.
When both migrations were run together with `rake db:migrate` the column
information in memory still referenced the old table structure.
Running the migrations separately fixed this, as a new connection was
then established before referencing the model. Explicitly calling
`reset_column_information` is a more reliable workaround.
Diffstat (limited to 'actionpack/lib/action_view/model_naming.rb')
0 files changed, 0 insertions, 0 deletions