Migrations create and modify the database tables HephaestusOban needs to function.

Usage

To use migrations in your application you'll need to generate an Ecto.Migration that wraps calls to HephaestusOban.Migration:

defmodule MyApp.Repo.Migrations.AddHephaestusOban do
  use Ecto.Migration

  def up, do: HephaestusOban.Migration.up()
  def down, do: HephaestusOban.Migration.down()
end

Isolation with Prefixes

HephaestusOban supports namespacing through PostgreSQL schemas (prefixes):

def up, do: HephaestusOban.Migration.up(prefix: "private")
def down, do: HephaestusOban.Migration.down(prefix: "private")

Versioning

Migrations are versioned and tracked via PostgreSQL table comments. Running up/1 will only apply migrations that haven't been run yet.

New installs can run all known versions:

def up, do: HephaestusOban.Migration.up()
def down, do: HephaestusOban.Migration.down()

Existing installs can upgrade incrementally to a specific version:

def up, do: HephaestusOban.Migration.up(version: 3)
def down, do: HephaestusOban.Migration.down(version: 2)

Use migrated_version/1 to inspect the recorded version:

HephaestusOban.Migration.migrated_version()
HephaestusOban.Migration.migrated_version(prefix: "private")