Name

sqitch-revert - Revert changes to a database

Synopsis

sqitch [options] revert
sqitch [options] revert <target>
sqitch [options] revert --to-target <target>

Description

Revert changes to the database. Starting from the current deployment state, changes will be reverted in reverse the order of application. All changes will be reverted unless a target is specified, either via --to or with no option flag, in which case changes will be reverted back to that target.

If the database has not been deployed to, or its state already matches the specified target, no changes will be made. If the target appears later in the plan than the currently-deployed state, an error will be returned, along with a suggestion to instead use sqitch-deploy.

Options

--to-target

--target

--to

Specify the reversion target. Defaults to reverting all changes. See sqitchchanges for the various ways in which change targets can be specified.

-s

--set

Set a variable name and value for use by the database engine client, if it supports variables. The format must be name=value, e.g., --set defuser='Homer Simpson'. Overrides any values loaded from the deploy.variables or revert.variables configurations.

--log-only

Log the changes as if they were reverted, but without actually running the revert scripts.

-y

Disable the prompt that normally asks whether or not to execute the revert.

Configuration Variables

[deploy.variables]

[revert.variables]

A section defining database client variables. The deploy.variables configuration is read from the deploy command configuration, on the assumption that the values will generally be the same. If they're not, use revert.variables to override deploy.variables.

These variables are Useful if your database engine supports variables in scripts, such as PostgreSQL's psql variables.

[revert.no_prompt]

A boolean value indicating whether or not to disable the prompt before executing the revert. My be overridden by -y.

Sqitch

Part of the sqitch suite.