Liquibase rollback in formatted sql not working

General Discussion
1

Hello,
rollback sql is not working for me, but output shows it is successful.
my sql
–liquibase formatted sql
–changeset vprasanth:145475548 failOnError:false
create table devopsrollback (
id int primary key,
name varchar(255)
);
–rollback drop table devopstag;

–changeset vprasanth:156514756 failOnError:false
create table devopstag1 (
id int primary key,
name varchar(255)
);
–rollback drop table devopstag1;

liquibase.property:
classpath: /etc/liquibase-4.4.3-bin/lib/postgresql-42.2.24.jar
username=xxxxx
password=yyyyy
url=jdbc:postgresql://:/testing
driver=org.postgresql.Driver
logFile=/var/log/liquibase.log
changelogfile=roll.sql

log file:

[2021-11-10 12:39:40] INFO [liquibase.database] Set default schema name to public
[2021-11-10 12:39:40] INFO [liquibase.lockservice] Successfully acquired change log lock
[2021-11-10 12:39:40] INFO [liquibase.changelog] Reading from public.databasechangelog
[2021-11-10 12:39:40] INFO [liquibase.lockservice] Successfully released change log lock
[2021-11-10 12:39:43] INFO [liquibase.lockservice] Successfully acquired change log lock
[2021-11-10 12:39:43] INFO [liquibase.hub] No operations will be reported. Simply add a liquibase.hub.apiKey setting to generate free deployment reports. Learn more at https://hub.liquibase.com
[2021-11-10 12:39:43] INFO [liquibase.hub] * Updated properties file liquibase.properties to set liquibase.hub.mode=off
[2021-11-10 12:39:43] INFO [liquibase.lockservice] Successfully released change log lock

2

Hi @prasanth1 ,

Thank you for sharing this example. Can you verify that you are using double dashes for the following:

--liquibase formatted sql
--changeset vprasanth:156514756 failOnError:false
create table devopstag1 (
id int primary key,
name varchar(255)
);
--rollback drop table devopstag1;

With this changeset, the rollback command should execute corresponding rollback code.

What rollback command are you using?

Sometimes, it is helpful to run liquibase history command before the rollback operation and after the rollback operation to ensure that changes have been rolled back successfully.

3

hey thanks buddy… i have resolved it with history cmd