Added sqlalchemy migration stub.

diff --git a/migration/README b/migration/README
new file mode 100644 (file)
index 0000000..6218f8c
--- /dev/null
+++ b/migration/README
@@ -0,0 +1,4 @@
+This is a database migration repository.
+
+More information at
+http://code.google.com/p/sqlalchemy-migrate/

diff --git a/migration/__init__.py b/migration/__init__.py
new file mode 100755 (executable)
index 0000000..e69de29

diff --git a/migration/manage.py b/migration/manage.py
new file mode 100644 (file)
index 0000000..0add9c2
--- /dev/null
+++ b/migration/manage.py
@@ -0,0 +1,4 @@
+#!/usr/bin/env python
+from migrate.versioning.shell import main
+
+main(repository='migration')

diff --git a/migration/migrate.cfg b/migration/migrate.cfg
new file mode 100644 (file)
index 0000000..9ed9017
--- /dev/null
+++ b/migration/migrate.cfg
@@ -0,0 +1,20 @@
+[db_settings]
+# Used to identify which repository this database is versioned under.
+# You can use the name of your project.
+repository_id=spline-users
+
+# The name of the database table used to track the schema version.
+# This name shouldn't already be used by your project.
+# If this is changed once a database is under version control, you'll need to 
+# change the table name in each database too. 
+version_table=migrate_version
+
+# When committing a change script, Migrate will attempt to generate the 
+# sql for all supported databases; normally, if one of them fails - probably
+# because you don't have that database installed - it is ignored and the 
+# commit continues, perhaps ending successfully. 
+# Databases in this list MUST compile successfully during a commit, or the 
+# entire commit will fail. List the databases your application will actually 
+# be using to ensure your updates to that database work properly.
+# This must be a list; example: ['postgres','sqlite']
+required_dbs=[]