database - flyway - a way to do distributed? -
i've been impressed amount of time flyway saves me doing basic things: creating schema scratch, , updating particular version.
i've been bit frustrated whenever out of ordinary happens: have customer-specific view needs applied schemas; have branch version has scripts base version not; i'd run same flyway installation on multiple schemas.
in of these cases, find myself manually moving .sql files around try different things; error-prone, , flyway has no forgiveness @ changing in history of schema. (this makes me bit antsy using flyway production schemas, that's topic).
it seems database-versioning has caught code versioning @ about, say, 2000: can have 1 single line of changes, , works great. in same way dvcs expanded experimentation , branching, there need in database versioning move in way.
is flyway thinking about, working on, or has ways i'm missing?
can't maintain 1 view implement feature toggling instead each customer? way maintain 1 schema , custom views break out logic "features." in property file or database table feature's toggle (true/false) determine how join or build sql.
Comments
Post a Comment