Rails migrations best practise- many similar migrations or one big?

Question

I have to add one column to almost 10 tables. What do you think is the best way to do that?

Make a one migration with weird name and use a loop to change column in each model
Make 10 migrations with similar content but having nice names like: add_extra_field_to_user

@denis Kind of. The goal is to add extra field for street name to each model that has an address data. — Piotr Brudny, Aug 02 '12 at 12:28
If any of them are the same address, you do not want to be duplicating it in different tables, but just referring to one table that contains the information. — Ari, Aug 02 '12 at 14:08

score 1 · Accepted Answer · answered Aug 02 '12 at 11:48

1

I would go for 10. Additional advantage is that you can run them, and rollback them seperately. Also I would always give readability priority, especially when otherwisee you get weird names ;)

answered Aug 02 '12 at 11:48

markijbema

3,985
20
32

Rails migrations best practise- many similar migrations or one big?

1 Answers1