Skip to content
This repository

Simple SQL change management

Prefer engine derived from target URI over the configuration.

Previously, `core.engine` was preferred over the value that could be derived
from a target URI. Now the target URI takes precedence over `core.engine`. The
`--engine` option still has highest precedence.

The upshot is that you no longer have to pass `--option` when deploying to a
target, as the engine can be inferred from the target's URI. This is true of
commands that take a target option or argument; those that don't will still
need to pass `--engine` to override any value in `core.engine`.

Resolves #152.
latest commit 2ef86baf97
David E. Wheeler authored
Octocat-spinner-32 bin Script should be executable. December 09, 2013
Octocat-spinner-32 dist Increment to v0.993. March 04, 2014
Octocat-spinner-32 etc Add Firebird templates December 16, 2013
Octocat-spinner-32 inc Fix "Cannot find deploy template" errors when installed into a local:… December 31, 2013
Octocat-spinner-32 lib Prefer engine derived from target URI over the configuration. March 25, 2014
Octocat-spinner-32 po Update language catalogs. March 04, 2014
Octocat-spinner-32 t Prefer engine derived from target URI over the configuration. March 25, 2014
Octocat-spinner-32 xt Spelling. March 04, 2014
Octocat-spinner-32 .gitignore Add .al to .gitignore December 16, 2013
Octocat-spinner-32 .travis.yml URI::db is now on CPAN. January 03, 2014
Octocat-spinner-32 Changes Prefer engine derived from target URI over the configuration. March 25, 2014
Octocat-spinner-32 MANIFEST.SKIP Exclude .travis.yml from the distribution. October 22, 2013
Octocat-spinner-32 README.md Increment to v0.993. March 04, 2014
Octocat-spinner-32 dist.ini Dump Git::CommitBuild. September 06, 2013
README.md

App/Sqitch version 0.993

Sqitch is a database change management application. It currently supports PostgreSQL 8.4 and higher, SQLite 3.7.11 and higher, MySQL 5.6.4 and higher,, and Oracle 10g and higher.

What makes it different from your typical migration approaches? A few things:

  • No opinions

    Sqitch is not integrated with any framework, ORM, or platform. Rather, it is a standalone change management system with no opinions about your database engine, application framework, or your development environment.

  • Native scripting

    Changes are implemented as scripts native to your selected database engine. Writing a PostgreSQL application? Write SQL scripts for psql. Writing an Oracle-backed app? Write SQL scripts for SQL*Plus.

  • Dependency resolution

    Database changes may declare dependencies on other changes -- even on changes from other Sqitch projects. This ensures proper order of execution, even when you've committed changes to your VCS out-of-order.

  • No numbering

    Change deployment is managed by maintaining a plan file. As such, there is no need to number your changes, although you can if you want. Sqitch doesn't much care how you name your changes.

  • Iterative Development

    Up until you tag and release your application, you can modify your change deployment scripts as often as you like. They're not locked in just because they've been committed to your VCS. This allows you to take an iterative approach to developing your database schema. Or, better, you can do test-driven database development.

Want to learn more? The best place to start is in the tutorials:

There have also been a number of presentations on Sqitch:

  • PDX.pm Presentation: Slides from "Sane Database Management with Sqitch", presented to the Portland Perl Mongers in January, 2013.

  • PDXPUG Presentation: Movie of "Sane Database Management with Sqitch", presented to the Portland PostgreSQL Users Group in September, 2012.

  • Agile Database Development: Slides from a three-hour tutorial session on using Git, test-driven development with pgTAP, and change management with Sqitch, updated in January, 2014.

Installation

Build Status

To install Sqitch from a distribution download, type the following:

perl Build.PL
./Build installdeps
./Build
./Build test
./Build install

If you're using Homebrew, you can use the Sqitch Homebrew Tap.

To build from a Git clone, first install Dist::Zilla, then use it to install Sqitch and its dependencies:

cpan Dist::Zilla
dzil install

To run Sqitch directly from the Git clone execute t/sqitch. If you're doing development on Sqitch, you will need to install the autoring dependencies, as well:

dzil listdeps | xargs cpan

Licence

Copyright © 2012-2014 iovation Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Something went wrong with that request. Please try again.