Can Liquibase write/Display Output logs of each sql changeset , similar to sqlplus.
The Current output says only success or failure , but does not show the full output
example : 0 rows updated is a success, but the user would now know that the actual update did not run
You can use sql-log-level=Info to echo the executed sql to the Liquibase output.
I have had an issue open since October 2022 regarding the “rows affected” confusion:
opened 12:50PM - 27 Oct 22 UTC
DBOracle
needs_response
<!--- This environment context section helps us quickly review your PR.
… Please take a minute to fill-out this information. -->
## Environment
**Liquibase Version**:
4.14
**Liquibase Integration & Version**: <Pick one: CLI, maven, gradle, spring boot, servlet, etc.>
CLI
**Liquibase Extension(s) & Version**:
**Database Vendor & Version**:
Oracle 19c
**Operating System Type & Version**:
Linux
**Infrastructure Type/Provider**: <AWC, GCS, Azure, VM, etc>
## Description
The "row(s) affected" output is very confusing for certain SQL statements in Oracle (may be in other platforms also)
1. DDL - Executions result in "0 row(s) affected"
[2022-10-26 21:06:38] INFO [liquibase.executor] CREATE OR REPLACE PROCEDURE SP_BIN_AUTOMATION (
...
END;
[2022-10-26 21:06:38] INFO [liquibase.executor] 0 row(s) affected
2. PL/SQL block - Executions result in "-1 row(s) affected"
[2022-10-26 20:51:31] INFO [liquibase.executor] BEGIN
update table set label = 'XYZ';
IF sql%rowcount != 1 THEN
RAISE_APPLICATION_ERROR( -20007, 'Expected number of rows to be updated is 1, but updated ' || sql%rowcount );
END IF;
END;
[2022-10-26 20:51:31] INFO [liquibase.executor] -1 row(s) affected
## Expected/Desired Behavior
No rows affected should be provided for either of these two scenarios.