My company are looking at replacing a bespoke db change control process with Liquibase and as part of that I’m looking the impact of what would be different if we do this. We use Oracle and our DB change scripts (changesets in Liquibase terms) cover DML as well as DDL operations and generally include a lot of DBMS_OUTPUT statements in them to say what the scripts are doing as they excute e.g : - ‘Inserting row for id X in table Y.’ etc,etc.
We would ideally like to preserve this capability if we move to a liquibase solution (that is to see the messages appear in the Liquibase output) as we need to be able to have an idea of what changesets are doing as they are applied to a schema. This is generally helpful when debugging any issues arising from the application of a changeset .
From what I can see there seems to be no way in Liquibase of making it DBMS_OUTPUT aware . Is this true ? Does anyone have any ideas of a workaround for this . My one idea is to write the dbms_output messages produced during execution of that change to a database table and , then have have a final changeset which always runs which selects the relevant data from this table - but I’m stuck on how to write Liquibase XML to do this .
Any advice would be much appreciated.