Whenever we change the table's schema from the migration using add_column, remove_column, change_column or anything else, the related model's column information doesn't get updated automatically and it becomes a stale object and gives errors on communicating with DB. The migrations are not properly documented for this... The migration doc looks like...
# Sometimes you'll want to add a column in a migration and populate it immediately after. In that case, you'll need
# to make a call to Base#reset_column_information in order to ensure that the model has the latest column data from
# after the new column was added. Example:
which is only specifying that you should call the method "reset_column_information" if the same model is immediately needed to populate the db... whereas the model remains stale even in the successive migrations without calling that method.
So, either the doc should be improved or the migrations should automatically call that method on all the models loaded on that time at the end of each migration.
