php - Is it good to rewrite your old db migration for unused column in your table? -
removing unused code practice. db migrations script file exception in practice?
i have maintain laravel application , i'm in process of cleaning unused code , found out have lots migrations scripts. migration includes adding , dropping table columns.
anyone have encountered same situation? thanks!
if migration not affect on database, fine remove them.
but, if affect, little part adding/removing (same or different) columns, changing types ... current data if in production; otherwise, refactoring before production good.
Comments
Post a Comment