Hello, thanks for the reply.
I tried what you suggested. But If I put the rollback statement on it’s own (like you suggested), it’s being executed along with the main SQL.
So, If I had a file like this,
–liquibase formatted sql
create table table_1 (
id int primary key,
drop table table_1;
insert into table_1(id, name) values (1, ‘name 1’);
insert into table_1(id, name) values (2, ‘name 2’);
delete from table_1 where id = 1;
delete from table_1 where id = 2;
The first changeset & rollback are executing one after the other and the change:2 set fails, as the previous rollback has dropped the table already.
Is my syntax wrong some where or am I missing a piece of config somewhere ?