Rails timestamps not updating dating a guy 20 years older
Since all I’m doing is updating an attribute, this is not efficient in memory or time.
You can think of each migration as being a new 'version' of the database.
Besides the double hash thing, the other option I can come up with is to not change update, but add the touch: false option to save and save! That way you can generally just do the assignment followed by an save!
(touch: false), and you can still wrap that in your own helper if the extra call really bothers you.
By the way, isn't this what we added no_touching for?
Migrations are a feature of Active Record that allows you to evolve your database schema over time.