3

I'm using Liquibase 3.1.1 to execute SQL scripts that create compiled database objects such as views, triggers, functions, and procedures.

Is there a changeset attribute that I can set to fail/abort the migration if the database object fails to compile?

For example, if I run a script that creates a trigger and that trigger fails to compile, how can I immediately stop the database migration?

Frank Calfo
  • 107
  • 1
  • 6
  • You can/should use [preconditions](http://www.liquibase.org/documentation/preconditions.html) to handle this. Also see this [answer](http://stackoverflow.com/a/1627524/332248) by @Nathan Voxland. – Jens Feb 11 '14 at 09:46

1 Answers1

1

Liquibase will automatically fail the upgrade if the database throws an error executing an SQL command. You can override the behavior with the changeSet failOnError attribute, but it defaults true which stops the database update.

If you are seeing Liquibase continue even with bad trigger SQL, your database must be allowing it to be created but then throwing runtime errors when executing it. In that case, you will need a changeSet after the create that checks the view, trigger, etc. either with a precondition or a tag that calls it.

Nathan Voxland
  • 15,453
  • 2
  • 48
  • 64