Explicit transaction boundaries or compensating actions after Ballerina schema change
In Ballerina, a transaction that includes a DDL statement may not reliably revert the database to its pre-change state upon rollback, because JDBC driver implementations vary in their treatment of transactional DDL. Some drivers silently absorb the change, others raise errors, and some leave partial artifacts, creating ambiguity across Ballerina versions and
ballerina