diff options
| author | Matt Riedemann <mriedem@us.ibm.com> | 2014-04-14 21:20:05 -0700 |
|---|---|---|
| committer | Matt Riedemann <mriedem@us.ibm.com> | 2014-04-15 19:22:03 -0700 |
| commit | 93efb62fd100f5135928443c2c325ae78b1c1fd0 (patch) | |
| tree | 925ed91aae536beaf767d3620de94d15a29326ca /migrate/tests/changeset/test_constraint.py | |
| parent | 07909159ae22dc0d399b9618dcf0f79a1d0332bf (diff) | |
| download | sqalchemy-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/tests/changeset/test_constraint.py')
| -rw-r--r-- | migrate/tests/changeset/test_constraint.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/migrate/tests/changeset/test_constraint.py b/migrate/tests/changeset/test_constraint.py index d27554e..6421206 100644 --- a/migrate/tests/changeset/test_constraint.py +++ b/migrate/tests/changeset/test_constraint.py @@ -274,7 +274,7 @@ class TestAutoname(CommonTestConstraint): self.table.insert(values={'id': 2, 'fkey': 2}).execute() self.table.insert(values={'id': 1, 'fkey': 3}).execute() - @fixture.usedb(not_supported=['oracle', 'sqlite']) + @fixture.usedb(not_supported=['oracle']) def test_autoname_unique(self): """UniqueConstraints can guess their name if None is given""" cons = UniqueConstraint(self.table.c.fkey) |