Ruby on Rails: Long list of migration files, common? -


is having long list of migration files common when building web application? seem adding long list of migration files because keep forgetting or keep thinking of adding column 'already' migrated database table.

having long list of migration files normal. it's 1 of best features of rails. think of them layers(like onion) stack on top of each other. if add new column or table , decide don't want anymore can rollback(peel away) latest changes. long have migration files can move , forth easily(don't recommend moving point). remember not delete migration files once raked unless rollback. when rollback , delete migration file make absolutely sure @ right layer(rollback point).

why? because example when clones app , runs migration file goes through migration files beginning end. if in middle messed or deleted won't able create database because goes through steps. hope helps.


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -