| ===== dbm-rollback-sql |
| |
| ====== Purpose |
| |
| Writes SQL to roll back the database to the state it was in when the tag was applied to STDOUT or a file. |
| |
| ====== Description |
| |
| Requires that the named tag exists. You can create tags with the <<ref-maintenance-scripts-dbm-tag,dbm-tag>> script. |
| |
| Usage: |
| [source,java] |
| ---- |
| grails <<environment>> dbm-rollback-sql <<tagName>> <<filename>> --contexts=<<contexts>> --defaultSchema=<<defaultSchema>> --dataSource=<<dataSource>> |
| ---- |
| |
| Required arguments: |
| |
| * `tagName` - The name of the tag to use |
| |
| Optional arguments: |
| |
| * `filename` - The path to the output file to write to. If not specified output is written to the console |
| * `contexts` - A comma-delimited list of http://www.liquibase.org/manual/contexts[context] names. If specified, only changesets tagged with one of the context names will be included |
| * `defaultSchema` - The default schema name to use |
| * `dataSource` - if provided will run the script for the specified dataSource. Not needed for the default dataSource. |
| |
| NOTE: Note that the `contexts`, `defaultSchema`, and `dataSource` parameter name and value must be quoted if executed in Windows, e.g. |
| [source,groovy] |
| ---- |
| grails dbm-rollback-sql "--contexts=<<contexts>>" "--defaultSchema=<<defaultSchema>>" --dataSource=<<dataSource>> |
| ---- |
| |
| NOTE: For the `dataSource` parameter, if the data source is configured as `reports` underneath the `dataSources` key in `application.[yml|groovy]`, the value should be `reports`. |
| |
| [source,groovy] |
| ---- |
| --dataSource=reports |
| ---- |
