summaryrefslogtreecommitdiff
path: root/migrate/changeset/schema.py
diff options
context:
space:
mode:
authorMatt Riedemann <mriedem@us.ibm.com>2014-04-14 21:20:05 -0700
committerMatt Riedemann <mriedem@us.ibm.com>2014-04-15 19:22:03 -0700
commit93efb62fd100f5135928443c2c325ae78b1c1fd0 (patch)
tree925ed91aae536beaf767d3620de94d15a29326ca /migrate/changeset/schema.py
parent07909159ae22dc0d399b9618dcf0f79a1d0332bf (diff)
downloadsqalchemy-migrate-93efb62fd100f5135928443c2c325ae78b1c1fd0.tar.gz
Move patch from oslo to drop unique constraints with sqlite
oslo-incubator commit 3f503faac for making sqlite work with dropping unique constraints in database migrations. This was made in oslo-incubator since at the time sqlalchemy-migrate was not in stackforge. Now that we can update sqlalchemy-migrate, move the patch over from oslo. This change also adds the support for the case that a unique constraint is dropped because the column it's on is dropped. Note that there are already unit tests that cover dropping a unique constraint directly and implicitly via dropping a column that is in the unique constraint. Related-Bug: #1307266 Change-Id: I5ee8082a83aebf66f6e1dacb093ed79e13f73f5e
Diffstat (limited to 'migrate/changeset/schema.py')
0 files changed, 0 insertions, 0 deletions