Custom SQL File

The “sqlFile” tag allows you to specify any sql statements and have it stored external in a file. It is useful for complex changes that are not supported through LiquiBase's automated refactoring tags such as stored procedures.

The sqlFile refactoring finds the file by searching in the following order:

1. The file is searched for in the classpath. This can be manually set and by default the liquibase startup script adds the current directory when run.
2. The file is searched for using the file attribute as a file name. This allows absolute paths to be used or relative paths to the working directory to be used.

The “sqlFile” tag can also support multiline statements in the same file. Statements can either be split using a ; at the end of the last line of the SQL or a go on its own on the line between the statements can be used.Multiline SQL statements are also supported and only a ; or go statement will finish a statement, a new line is not enough. Files containing a single statement do not need to use a ; or go.

The sql file can also contain comments of either of the following formats:

1. A multiline comment that starts with /* and ends with */.
2. A single line comment starting with <space>–<space> and finishing at the end of the line

<sqlFile path="sample.sql"/>

where sample.sql can contain:

INSERT INTO person (id, name) VALUES (1, 'Bob')

A multiline sample.sql might look like:

INSERT INTO person (id,name) VALUES (1, 'George');
INSERT INTO person (id,name) VALUES (2, 'Jim')

For MSSQL you could also use go for multiline support and have statements split across many lines:

INSERT INTO person (id,name) 
VALUES (1, 'George')
go
INSERT INTO person (id,name) 
VALUES (2, 'Jim')

Automatic Rollback Support: NO