Not to generate change sql when nothing to migrate

General Discussion
1

Hi,

Is it possible to tell liquibase not to generate any output when using migrate-sql when there was no change?

Rgds
T

2

If it doesn’t do it by default, it is not configurable. 

You don’t want any file generated? I think it makes an empty file, doesn’t it?

Nathan

3

It generates the comment header and

SELECT COUNT(*) FROM DATABASECHANGELOGLOCK WHERE ID=1;

SELECT COUNT(*) FROM DATABASECHANGELOGLOCK WHERE ID=1;

– Release Database Lock
UPDATE DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE  ID = 1;

It would be nice not to generate any file if there is no change.

The reason is the following. We have no direct access to the production database so we cannot use migrate. Because of that we need to generate pure sql via migrate-sql and send that over.
We are using bamboo. The goal would be that when we run a bamboo build it either produces .sql changes as artifacts or not. And when we create a production package we just take all the generated sql files (if any) starting from a certain build number and have them as a package.