migrations 0.1.1

Status

The project is in beta now. Bugs and breaking changes may occur.

Features

• No specific database requirements, use it for anything you call database.

• Pretty simple, just generate migration script and define self-explanatory up() and down() functions there.

• Use imports in your migration scripts to load database bindings. Talk to the database the same way your application does.

• Stores the sequence of already performed migrations. If the sequence does not match scripts in migrations directory (e.g. after merge), aborts and warns user.

• TBD: Deeply configurable, including resources acquiring and releasing.

Requirements

Only Python 3 is supported for now.

Installation

$ pip install migrations

Notice, this distribution provides package and executable script named migrate, so check if it does not mess with existing packages/scripts. Generally, you should neither install this tool globally, nor install several migration tools for one project.

Usage

usage: migrate [options] [action]

actions:
  up     [-h] [NAME|COUNT]   (default) perform COUNT migrations or till
                             given NAME (by default perform all available)
  down   [-h] [NAME|COUNT]   revert COUNT migrations or till
                             given NAME (by default revert one)
  create [-h]  NAME          create new migration file

  show   [-h]                print all migrations in chronological order

options:
  -h, --help                 show this help message and exit
  -v, --version              show version and exit
  -d PATH, --migrations-dir PATH
                             directory where migrations are stored
  -s PATH, --state-file PATH
                             location of file which stores database state
  -t PATH, --template-file PATH
                             location of template file for new migrations

Each migration file must define functions up() and down() without required arguments.

Simple migration example:

import redis

db = redis.Redis(host='localhost', port=6379)

def up():
    db.rpush('used_libraries', 'migrations')

def down():
    db.rpop('used_libraries', 'migrations')

Current working directory is prepended to sys.path, so any import statement in migration file tries to find requested module in working directory at first. You can use this to manage database access for your both app and migrations with single piece of code. See an example. Let’s assume that in working directory we have module named db, which contains singleton object responsible for DB connection, for example PyMySQL Connection object.

from db import connection

def manage_cursor(action):
    def wrap():
        with connection.cursor() as cursor:
            action(cursor)
        connection.commit()
    return wrap

@manage_cursor
def up(cursor):
    cursor.execute(
        "INSERT INTO used_libraries (`name`) VALUES ('migrations')"
    )

@manage_cursor
def down(cursor):
    cursor.execute(
        "DELETE FROM used_libraries WHERE `name`='migrations'"
    )