Boxfuse 
Validate applied migrations against resolved ones (on the filesystem or classpath) to detect accidental changes that may prevent the schema(s) from being recreated exactly.
Validation fails if
> flyway [options] validate
| Option | Required | Default | Description |
|---|---|---|---|
| url | YES | The jdbc url to use to connect to the database | |
| driver | NO | Auto-detected based on url | The fully qualified classname of the jdbc driver to use to connect to the database |
| user | NO | The user to use to connect to the database | |
| password | NO | The password to use to connect to the database | |
| schemas | NO | default schema of the connection | Comma-separated case-sensitive list of schemas managed by Flyway. The first schema will be the one containing the metadata table. |
| table | NO | schema_version | The name of Flyway's metadata table. By default (single-schema mode) the metadata table is placed in the default schema for the connection provided by the datasource. When the flyway.schemas property is set (multi-schema mode), the metadata table is placed in the first schema of the list. |
| locations | NO | Comma-separated list of locations to scan recursively for migrations. The location type is determined by its prefix. Unprefixed locations or locations starting with classpath: point to a package on the classpath and may contain both sql and java-based migrations.Locations starting with filesystem: point to a directory on the filesystem and may only contain sql migrations.
|
|
| jarDirs | NO | Comma-separated list of directories containing JDBC drivers and Java-based migrations | |
| sqlMigrationPrefix | NO | V | The file name prefix for Sql migrations |
| repeatableSqlMigrationPrefix | NO | R | The file name prefix for repeatable Sql migrations |
| sqlMigrationSeparator | NO | __ | The file name separator for Sql migrations |
| sqlMigrationSuffix | NO | .sql | The file name suffix for Sql migrations |
| encoding | NO | UTF-8 | The encoding of Sql migrations |
| placeholderReplacement | NO | true | Whether placeholders should be replaced |
| placeholders.name | NO | Placeholders to replace in Sql migrations | |
| placeholderPrefix | NO | ${ | The prefix of every placeholder |
| placeholderSuffix | NO | } | The suffix of every placeholder |
| resolvers | NO | Comma-separated list of fully qualified class names of custom MigrationResolver implementations to be used in addition to the built-in ones for resolving Migrations to apply. | |
| skipDefaultResolvers | NO | false | Whether default built-in resolvers (sql, jdbc and spring-jdbc) should be skipped. If true, only custom resolvers are used. |
| callbacks | NO | Comma-separated list of fully qualified class names of FlywayCallback implementations to use to hook into the Flyway lifecycle. | |
| skipDefaultCallbacks | NO | false | Whether default built-in callbacks (sql) should be skipped. If true, only custom callbacks are used. |
| target | NO | latest version | The target version up to which Flyway should consider migrations. Migrations with a higher version number will be ignored. The special value current designates the current version of the schema.
|
| outOfOrder | NO | false | Allows migrations to be run "out of order".
If you already have versions 1 and 3 applied, and now a version 2 is found, it will be applied too instead of being ignored. |
| cleanOnValidationError | NO | false | Whether to automatically call clean or not when a validation error occurs. This is exclusively intended as a convenience for development. Even tough we strongly recommend not to change migration scripts once they have been checked into SCM and run, this provides a way of dealing with this case in a smooth manner. The database will be wiped clean automatically, ensuring that the next migration will bring you back to the state checked into SCM. Warning ! Do not enable in production ! |
| ignoreMissingMigrations | NO | false | Ignore missing migrations when reading the metadata table. These are migrations that were performed by an older deployment of the application that are no longer available in this version. For example: we have migrations available on the classpath with versions 1.0 and 3.0. The metadata table indicates that a migration with version 2.0 (unknown to us) has also been applied. Instead of bombing out (fail fast) with an exception, a warning is logged and Flyway continues normally. This is useful for situations where one must be able to deploy a newer version of the application even though it doesn't contain migrations included with an older one anymore. |
| ignoreFutureMigrations | NO | true | Ignore future migrations when reading the metadata table. These are migrations that were performed by a newer deployment of the application that are not yet available in this version. For example: we have migrations available on the classpath up to version 3.0. The metadata table indicates that a migration to version 4.0 (unknown to us) has already been applied. Instead of bombing out (fail fast) with an exception, a warning is logged and Flyway continues normally. This is useful for situations where one must be able to redeploy an older version of the application after the database has been migrated by a newer one. |
flyway.driver=org.hsqldb.jdbcDriver flyway.url=jdbc:hsqldb:file:/db/flyway_sample flyway.user=SA flyway.password=mySecretPwd flyway.schemas=schema1,schema2,schema3 flyway.table=schema_history flyway.locations=classpath:com.mycomp.migration,database/migrations,filesystem:/sql-migrations flyway.sqlMigrationPrefix=Migration- flyway.repeatableSqlMigrationPrefix=RRR flyway.sqlMigrationSeparator=__ flyway.sqlMigrationSuffix=-OK.sql flyway.encoding=ISO-8859-1 flyway.placeholderReplacement=true flyway.placeholders.aplaceholder=value flyway.placeholders.otherplaceholder=value123 flyway.placeholderPrefix=#[ flyway.placeholderSuffix=] flyway.resolvers=com.mycomp.project.CustomResolver,com.mycomp.project.AnotherResolver flyway.skipDefaultCallResolvers=false flyway.callbacks=com.mycomp.project.CustomCallback,com.mycomp.project.AnotherCallback flyway.skipDefaultCallbacks=false flyway.target=5.1 flyway.outOfOrder=false flyway.cleanOnValidationError=false flyway.ignoreMissingMigrations=false flyway.ignoreFutureMigrations=false
> flyway validate Flyway 4.2.0 by Boxfuse No migrations applied yet. No validation necessary.