Inefficient multi tenant update

Description

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.

Environment

Multi tenant

Activity

Show:

Details

Reporter

Components

Fix versions

Affects versions

Priority

Created March 11, 2015 at 4:25 PM
Updated March 11, 2015 at 9:19 PM