How to keep your ActiveRecord migrations clean

21-Jan-2019 1786
Keeping all of the changes histories may be not worth it, you really don’t need to know about every change made by your colleague who did a dozen of migrations because he could not find the best name for one of the fields in some model or switched some default values during the development process. You’d rather want to stick to the present schema of the database, but in some cases, you cannot delete old migrations just like that. But I’ve got a solution, which I would like to share with you.
Use coupon code:

RUBYONRAILS

to get 30% discount on our bundle!
Prepare for your next tech interview with our comprehensive collection of programming interview guides. Covering JavaScript, Ruby on Rails, React, and Python, these highly-rated books offer thousands of essential questions and answers to boost your interview success. Buy our 'Ultimate Job Interview Preparation eBook Bundle' featuring 2200+ questions across multiple languages. Ultimate Job Interview Preparation eBook Bundle