When applying the same changelog to several data sources / schemas (as in MultiTenantSpringLiquibase) the current design means that the changelog needs to parsed once for every time it needs to be applied. If a DatabaseChangeLog object could be reused for several applications it would save time with big changelogs and many data sources / schemas.
When applying the same changelog to several data sources / schemas (as in MultiTenantSpringLiquibase) the current design means that the changelog needs to parsed once for every time it needs to be applied. If a DatabaseChangeLog object could be reused for several applications it would save time with big changelogs and many data sources / schemas.