generateChangeLog memory optimization

Description

We have found generateChangeLog to be an excellent way to migrate databases on regular basis. With a little help of xsl transformation, migration can become nicely automated. Anyway on bigger amount of data, memory consumption of liquibase gets too high and export is simply impossible.

From what I have seen in the source code, this probably happens because the xml output is not started until the whole bunch of data is read into memory.

Environment

None

Activity

Show:

Nathan Voxland September 13, 2011 at 5:47 AM

diff improvements will be in 2.1

Details

Reporter

Affects versions

Priority

Created February 8, 2011 at 11:47 AM
Updated June 12, 2013 at 9:39 PM