Katrina Owen a1d2f69377 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.		2012-10-10 23:44:43 +02:00
..
assets	[Guides] Format content for small devices	2012-10-06 16:40:51 -04:00
code/getting_started	Remove duplicate 'the' article in commented line	2012-10-08 14:00:59 -07:00
rails_guides	[Guides] Navigation styling for small devices	2012-10-06 16:38:37 -04:00
source	Expand caveat about models in migrations (rails guide)	2012-10-10 23:44:43 +02:00
CHANGELOG.md	Update test locations	2012-10-09 17:53:56 -06:00
rails_guides.rb
Rakefile
w3c_validator.rb