Changes for version 0.950 - 2013-01-03
- Fixed the "Name" header in `sqitch-rebase` so that it will actually show up on the CPAN search sites.
- Fixed test failure triggered by the passage of time in `t/engine.t`.
- At the start of a `deploy`, if the most recently deployed change has any unlogged tags (that is, tags added since the last `deploy`), they will be logged before the `deploy` continues (issue #60).
- Added the `--no-log` option to `deploy`, `revert`, and `rebase`. This causes the changes to be logged as deployed without actually running the deploy scripts. Useful for an existing database that is being converted to Sqitch, and you need to log changes as deployed because they have been deployed by other means in the past.
- Now check that dependencies are required for all changes to be deployed or reverted before deploying or reverting anything, rather than checking dependencies for each change just before deploying or reverting it. This allows a or revert deploy to fail sooner, with no database changes, when dependencies are not met.
- The `deploy` command now check that no changes its about to deploy are already deployed.
- Added `--mode` to the `rebase` command.
- Added the `--verify` option to `deploy` and `rebase`. Specify this option to run the verify script, if it exists, for each change after it is deployed. If the verify script dies, the deploy will be considered a failure and the requisite reversion (as specified for `--mode`) will begin.
- Added the `verify` command, which verifies that a database is valid relative to the plan and each deployed change's verification scripts.
- Changed the format of the list of changes output by `deploy` and `revert` so that each now gets "ok" or "not ok" printed on success or failure.
- Added short aliases for commonly-used core options:
- -f for --plan-file
- -v for --verbose
- -h for --db-host
- -p for --db-port
Documentation
Sqitch add usage statement
Add a database change to the plan
Sqitch bundle usage statement
Bundle a Sqitch project for distribution
Sqitch config usage statement
Get and set local, user, or system Sqitch options
Sqitch deploy usage statement
Deploy changes to a database
Sqitch help usage statement
Display help for Sqitch and Sqitch commands
Sqitch init usage statement
Create a new Sqitch project
Sqitch log usage statement
Show database change logs
Sqitch rebase usage statement
Revert and redeploy database changes
Sqitch revert usage statement
Revert changes to a database
Sqitch rework usage statement
Rework a database change
Sqitch show usage statement
Show object information or change file contents
Sqitch status usage statement
Show the current deployment status of a database
Sqitch tag usage statement
Create or list tag objects
Sqitch verify usage statement
Verify deployed database changes
Sane database change management
List of common sqitch commands
A tutorial introduction to Sqitch
Modules
Sane database change management
Sqitch Command support
Add a new change to a Sqitch plan
Bundle Sqitch changes for distribution
Get and set local, user, or system Sqitch options
Deploy Sqitch changes to a database
Display help information about Sqitch
Initialize a Sqitch project
Show a database event log
Revert and redeploy Sqitch changes
Revert Sqitch changes from a database
Rework a Sqitch change
Show Sqitch changes to a database
Display status information about Sqitch
Add or list tags in a Sqitch plan
Verify deployed Sqitch changes
Sqitch configuration management
Sqitch DateTime object
Sqitch Deployment Engine
Sqitch PostgreSQL Engine
Sqitch SQLite Engine
Sqitch Deployment Plan
Sqitch deployment plan blank line
Sqitch deployment plan tag
Sqitch deployment plan change list
Sqitch dependency specification
Sqitch deployment plan line
Sqitch deployment plan line list
Sqitch deployment plan blank line
Sqitch deployment plan tag
Sqitch Exception class