When we generate the SQL statements for a changeset, the updates/Inserts to the DATABASECHANGELOG table also are created. This is good, but in case the SQL statement fails, still the change log statement is executed leaving the database in a inconsistent state even from a Liquibase perspective. Can these SQL generated also include transaction statements to avoid this?