Classes in this File | Line Coverage | Branch Coverage | Complexity | ||||
SqlStatement |
|
| 1.0;1 |
1 | package liquibase.statement; | |
2 | ||
3 | /** | |
4 | * The SqlStatement classes correspond to (roughly) a single SQL statement. SqlStatement instances are created by Change | |
5 | * classes, and by Liquibase itself as the primary database-independent abstraction of statments to execute against a | |
6 | * database. | |
7 | * <p> | |
8 | * A single SqlStatement may yield multiple SQL commands, and may yield a different number of SQL commands depending on | |
9 | * the database. If a particular statement. The SqlStatement implementations do not actually generate SQL strings, that | |
10 | * is left to the SqlGenerator implementations. Instead, the purpose of the SqlStatement implementation is to hold the | |
11 | * metadata required to generate the correct SQL for a particular database at a later time. | |
12 | * | |
13 | * @see liquibase.change.Change | |
14 | * @see liquibase.sqlgenerator.SqlGenerator | |
15 | * @see liquibase.sqlgenerator.SqlGeneratorFactory | |
16 | */ | |
17 | public interface SqlStatement { | |
18 | ||
19 | boolean skipOnUnsupported(); | |
20 | ||
21 | } |