The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.
 / 
App-Sqitch-0.980
River stage one • 2 direct dependents • 2 total dependents
43 ++

Changes for version 0.980 - 2013-08-28

  • Changed the default SQLite Sqitch database name from `$dbname-sqitch.$suffix` to `sqitch.$suffix`. The `$suffix` still comes from the destination database name. This breaks compatibility with previous releases. If you need the old name, set it with `sqitch config core.sqlite.sqitch_db $dbname`.
  • Fixed encoding of the user's full name when fetched from the system on OS X. Thanks to Tomohiro Hosaka for the pull request!
  • Fixed test failures when DBD::SQLite is installed but compiled with SQLite 3.7.10 or lower.
  • Fixed a bug where declaring a dependency on a reworked change would incorrectly result in the error "Key "foo" matches multiple changes". Thanks to BryLo for the report (issue #103).
  • Modified tests to allow them to run in parallel without stomping on each other.
  • Bundling of options, such as `-vvv`, now works properly (issue #108).
  • Added alias `--get-regexp` for `--get-regex` to the `config` command. This brings it in line with the documentation for the `config` command (Issue #110).
  • Fixed all of the `config` command actions that contain a dash so that they actually work. Thanks to Ștefan Suciu for the report (issue #110).
  • All leading and trailing white space is now trimmed from plan notes, rather than just vertical white space. Thanks to Ronan Dunklau for the report (issue #106).
  • The `status` command now notices if the specified database is uninitialized and says as much, rather than dying with an SQL error (issue #109).
  • When reading the user's name from the system to generate the default value of the `user.name` config, Sqitch now uses Encode::Locale to try to decode the value from the system encoding. Note that this is not necessary if `user.name` is explicitly set, as recommended. Issue #107.
  • Compatibility change: Changed the location and name of script template files. Previously they were called `deploy.tmpl`, `revert.tmpl`, and `verify.tmpl`, and they lived in the `templates` subdirectory of the system-wide and user-specific configuration directories. They now live in subdirectories of the `templates` directory named for each action (deploy, revert, and verify), and with file names matching engine names (`pg.tmpl`, `sqlite.tmpl`, `oracle.tmpl`, and `mysql.tmpl`). The installer will move old files from the system-wide config directory (`sqitch --etc-path`) to their new homes, named `pg.tmpl` and `sqlite.tmpl`. It assumes no customizations exist for Oracle. If that's not true in your case, simply copy the `pg.tmpl` files to `oracle.tmpl`.
  • Added the `--template-name` option to the `add` command. By default, it looks for templates named for the current engine. The option allows for the user of task-specific templates. For example, if you create templates named `createtable.tmpl` in the `deploy`, `revert`, and `verify` subdirectories of `~/.sqitch/templates`, You can specify `--template-name createtable` to use those templates when adding a change.
  • Added the `--exists` option to the `show` command.
  • Fixed the `--set` option to the `add` command so that duplicate keys have their values passed to the template as an array, as documented.
  • If Template::Toolkit is installed, the `add` command will use it for processing templates instead of Template::Tiny. This makes it easy to upgrade the templating environment just by installing a module.

Documentation

sqitch-add-usage
Sqitch add usage statement
sqitch-add
Add a database change to the plan
sqitch-bundle-usage
Sqitch bundle usage statement
sqitch-bundle
Bundle a Sqitch project for distribution
sqitch-checkout-usage
Sqitch checkout usage statement
sqitch-checkout
Revert, checkout another VCS branch, and re-deploy changes
sqitch-config-usage
Sqitch config usage statement
sqitch-config
Get and set local, user, or system Sqitch options
sqitch-deploy-usage
Sqitch deploy usage statement
sqitch-deploy
Deploy changes to a database
sqitch-help-usage
Sqitch help usage statement
sqitch-help
Display help for Sqitch and Sqitch commands
sqitch-init-usage
Sqitch init usage statement
sqitch-init
Create a new Sqitch project
sqitch-log-usage
Sqitch log usage statement
sqitch-log
Show database change logs
sqitch-plan-usage
Sqitch plan usage statement
sqitch-plan
Show planned database changes
sqitch-rebase-usage
Sqitch rebase usage statement
sqitch-rebase
Revert and redeploy database changes
sqitch-revert-usage
Sqitch revert usage statement
sqitch-revert
Revert changes to a database
sqitch-rework-usage
Sqitch rework usage statement
sqitch-rework
Rework a database change
sqitch-show-usage
Sqitch show usage statement
sqitch-show
Show object information or change file contents
sqitch-status-usage
Sqitch status usage statement
sqitch-status
Show the current deployment status of a database
sqitch-tag-usage
Sqitch tag usage statement
sqitch-tag
Create or list tag objects
sqitch-verify-usage
Sqitch verify usage statement
sqitch-verify
Verify deployed database changes
sqitch
Sane database change management
sqitchchanges
sqitchcommands
List of common sqitch commands
sqitchtutorial-mysql
A tutorial introduction to Sqitch change management on MySQL
sqitchtutorial-oracle
A tutorial introduction to Sqitch change management on Oracle
sqitchtutorial-sqlite
A tutorial introduction to Sqitch change management on SQLite
sqitchtutorial
A tutorial introduction to Sqitch
sqitchusage
Sqitch usage statement

Modules

App::Sqitch
Sane database change management
App::Sqitch::Command
Sqitch Command support
App::Sqitch::Command::add
Add a new change to a Sqitch plan
App::Sqitch::Command::bundle
Bundle Sqitch changes for distribution
App::Sqitch::Command::checkout
Revert, change checkout a VCS branch, and redeploy
App::Sqitch::Command::config
Get and set local, user, or system Sqitch options
App::Sqitch::Command::deploy
Deploy Sqitch changes to a database
App::Sqitch::Command::help
Display help information about Sqitch
App::Sqitch::Command::init
Initialize a Sqitch project
App::Sqitch::Command::log
Show a database event log
App::Sqitch::Command::plan
List the changes in the plan
App::Sqitch::Command::rebase
Revert and redeploy Sqitch changes
App::Sqitch::Command::revert
Revert Sqitch changes from a database
App::Sqitch::Command::rework
Rework a Sqitch change
App::Sqitch::Command::show
Show Sqitch changes to a database
App::Sqitch::Command::status
Display status information about Sqitch
App::Sqitch::Command::tag
Add or list tags in a Sqitch plan
App::Sqitch::Command::verify
Verify deployed Sqitch changes
App::Sqitch::Config
Sqitch configuration management
App::Sqitch::DateTime
Sqitch DateTime object
App::Sqitch::Engine
Sqitch Deployment Engine
App::Sqitch::Engine::mysql
Sqitch MySQL Engine
App::Sqitch::Engine::oracle
Sqitch Oracle Engine
App::Sqitch::Engine::pg
Sqitch PostgreSQL Engine
App::Sqitch::Engine::sqlite
Sqitch SQLite Engine
App::Sqitch::ItemFormatter
Format events and changes for command output
App::Sqitch::Plan
Sqitch Deployment Plan
App::Sqitch::Plan::Blank
Sqitch deployment plan blank line
App::Sqitch::Plan::Change
Sqitch deployment plan tag
App::Sqitch::Plan::ChangeList
Sqitch deployment plan change list
App::Sqitch::Plan::Depend
Sqitch dependency specification
App::Sqitch::Plan::Line
Sqitch deployment plan line
App::Sqitch::Plan::LineList
Sqitch deployment plan line list
App::Sqitch::Plan::Pragma
Sqitch deployment plan blank line
App::Sqitch::Plan::Tag
Sqitch deployment plan tag
App::Sqitch::Role::DBIEngine
An engine based on the DBI
App::Sqitch::Role::RevertDeployCommand
A command that reverts and deploys
App::Sqitch::X
Sqitch Exception class

Other files