The postgresql-simple-migration package

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain]

A PostgreSQL-simple schema migration utility


[Skip to ReadMe]

Properties

Versions0.1.0.0, 0.1.0.0, 0.1.1.0, 0.1.2.0, 0.1.3.0, 0.1.5.0, 0.1.6.0, 0.1.7.0, 0.1.8.0, 0.1.9.0, 0.1.10.1, 0.1.11.0
Change logNone available
Dependenciesbase (>=4.6 && <5.0), base64-bytestring (==1.0.*), bytestring (==0.10.*), cryptohash (==0.11.*), directory (==1.2.*), postgresql-simple (==0.4.*) [details]
LicenseBSD3
Copyright2014, Andreas Meingast
AuthorAndreas Meingast <ameingast@gmail.com>
MaintainerAndreas Meingast <ameingast@gmail.com>
CategoryDatabase
Home pagehttps://github.com/ameingast/postgresql-simple-migration
Bug trackerhttps://github.com/ameingast/postgresql-simple-migration/issues
Source repositoryhead: git clone git://github.com/ameingast/postgresql-simple-migration
Executablesmigrate
UploadedSat Jul 5 05:10:15 UTC 2014 by ameingast

Modules

[Index]

Downloads

Maintainers' corner

For package maintainers and hackage trustees


Readme for postgresql-simple-migration-0.1.0.0

[back to package description]

PostgreSQL Migrations for Haskell

Build Status

Welcome to postgresql-simple-migrations, a tool for helping you with PostgreSQL schema migrations.

This project is an open-source database migration tool. It favors simplicity over configuration.

It is implemented in Haskell and uses the (excellent) postgresql-simple library to communicate with PostgreSQL.

It comes in two flavors: a library that features an easy to use Haskell API and as a standalone application.

Database migrations can be written in SQL (in this case PostgreSQL-sql) or in Haskell.

Why?

Database migrations should not be hard. They should be under version control and documented in both your production systems and in your project files.

What?

This library executes SQL/Haskell migration scripts and keeps track of their meta information.

Scripts are be executed exactly once and any changes to scripts will cause a run-time error notifying you of a corrupted database.

The meta information consists of:

How?

This utility can be used in two ways: embedded in your Haskell program or as a standalone binary.

Standalone

The standalone program supports file-based migrations. To execute all SQL-files in a directory $BASE_DIR, execute the following command to initialize the database in a first step.

CON="host=$host dbname=$db user=$user password=$pw"
./dist/build/migrate/migrate init $CON
./dist/build/migrate/migrate migrate $CON $BASE_DIR

For more information about the PostgreSQL connection string, see: libpq-connect.

Library

The library supports more actions than the standalone program.

Initializing the database:

main :: IO ()
main = do
    let url = "host=$host dbname=$db user=$user password=$pw"
    con <- connectPostgreSQL (BS8.pack url)
    void $ runMigration $ MigrationContext MigrationInitialization True con

For file-based migrations, the following snippet can be used:

main :: IO ()
main = do
    let url = "host=$host dbname=$db user=$user password=$pw"
    let dir = "."
    con <- connectPostgreSQL (BS8.pack url)
    void $ runMigration $ MigrationContext (MigrationDirectory dir) True con

To run Haskell-based migrations, use this:

main :: IO ()
main = do
    let url = "host=$host dbname=$db user=$user password=$pw"
    let name = "my script"
    let script = "create table users (email varchar not null)";
    con <- connectPostgreSQL (BS8.pack url)
    void $ runMigration $ MigrationContext (MigrationScript name script) True con

Compilation and Tests

The program is built with the cabal build system. The following command builds the library, the standalone binary and the test package.

cabal configure --enable-tests && cabal build -j

To execute the tests, you need a running PostgreSQL server with an empty database called test. Tests are executed through cabal as follows:

cabal configure --enable-tests && cabal test

To Do