Consider adding reset_column_information to Backfilling data recommendations

[alexeyr-ci1]

When we follow Backfilling data: Good, we found that sometimes when the migrations run immediately one after another, cached column information seems to be used and User.reset_column_information needs to be used in the second migration.

Unfortunately, this is hard to reproduce. In our project it happened when adding a translation column with the mobility gem and backfilling it from the non-translation column.

[niudage]

good