DEV Community

Discussion on: Purify code with data integrity. Part 1: defaults and not-nulls

Collapse
 
neznauy profile image
Alexandr Shlyakov

Thanks for ur article.
I think, it's not good practice to place changing data rake tasks in migration, cause of u can change model name, column name, etc. in future, and this migration will fail and make suffer developers who deploy project locally.
Although it's ok to make one-time used rake for production, but in development or test env u should actualize data from seed or dump.
It's only my opinion =)