summaryrefslogtreecommitdiffstats
path: root/tests/backend_db2.conf
diff options
context:
space:
mode:
authorBrant Knudson <bknudson@us.ibm.com>2013-06-07 14:47:49 -0500
committerBrant Knudson <bknudson@us.ibm.com>2013-07-01 11:07:40 -0500
commit052e7d525146c235f3c4ddc729ee6e1ac18a1337 (patch)
treeebdad760836d830a6a187b1b26bba6590017c486 /tests/backend_db2.conf
parent6362fb73eda13e7710226a72a083ad9918410bd9 (diff)
downloadkeystone-052e7d525146c235f3c4ddc729ee6e1ac18a1337.tar.gz
keystone-052e7d525146c235f3c4ddc729ee6e1ac18a1337.tar.xz
keystone-052e7d525146c235f3c4ddc729ee6e1ac18a1337.zip
DB2 migration support
DB2 will not allow you to rename a table if it's got a constraint on it (a unique or foreign key constraint). This fix changes the migrations so that the unique or FK constraints are dropped from tables before renaming and then restoring the unique FK constraints. This works for DB2 and other DBMSs that support FK constraints such as MySQL with InnoDB and PostgreSQL. Also, for DB2, give a name to the unique constraints so that they can be manipulated. Fixes bug 1188785 Change-Id: I7cf6ab42084e43d827ed827c64025e61e72a4672
Diffstat (limited to 'tests/backend_db2.conf')
-rw-r--r--tests/backend_db2.conf4
1 files changed, 4 insertions, 0 deletions
diff --git a/tests/backend_db2.conf b/tests/backend_db2.conf
new file mode 100644
index 00000000..44032255
--- /dev/null
+++ b/tests/backend_db2.conf
@@ -0,0 +1,4 @@
+#Used for running the Migrate tests against a live DB2 Server
+#See _sql_livetest.py
+[sql]
+connection = ibm_db_sa://keystone:keystone@/staktest?charset=utf8