rails: best proceed changes prolongation database
i need changes an in-use prolongation database. only adding few columns. i've finished changes dev database migrations. best proceed transform prolongation database while preserving existent information disrupting operation too much?
it's mysql i wanting supplement information columns good already existent records. buttress have default value (it's boolean) nonetheless timestamp should have an erratic backdated value. quarrel depends huge.
so i migrations i supplement information i only twin (or 3 - i supplement information -latest migrations prolongation db wasn't primarily built around migrations (i trust used schema instead)?
Comments
Post a Comment