php - A lot of database migrations files -
i'm using database migrations php symfony framework , noticed there lot of files, , when build project , every time many files (migrations) executed.
what best practice manage migrations? delete them , create 1 database dump file, database initiation?
i'm assuming you're using doctrine migrations create these files. on dev can regenerate database using doctrine:schema:update command. when setting new instance can use doctrine:schema:create command create latest table definitions you.
that brings question; need keep migrations? long know migrations have been executed on outdated instances can safely archive (my preferred option) or delete them never called again.
Comments
Post a Comment