diff options
| author | Matt Riedemann <mriedem@us.ibm.com> | 2014-07-18 11:42:38 -0700 |
|---|---|---|
| committer | Matt Riedemann <mriedem@us.ibm.com> | 2014-08-04 07:34:08 -0700 |
| commit | 7bb74f70e9d239a488e0c909c28b4131dbfd5067 (patch) | |
| tree | 3b501a3079e5c7653bfe841d623c2e0fcc051dd9 /requirements.txt | |
| parent | 942e03b2b19f38ea56803221e30f1cc0b461c4b6 (diff) | |
| download | sqalchemy-migrate-7bb74f70e9d239a488e0c909c28b4131dbfd5067.tar.gz | |
Fix ibmdb2 unique constraint handling for sqlalchemy 0.9
The ibmdb2 unique constraint code was accessing the private _all_cols
member var in iterating over columns which breaks in sqlalchemy 0.9 so
fix up the code to not use internals of sqlalchemy.
UniqueConstraint in sqlalchemy extends ColumnCollectionConstraint
which implements __iter__ to generate a tuple of the columns in
the constraint, so we just iterate over the constraint as the fix.
This is based on a patch from Rahul Priyadarshi in ibm-db-sa issue
158:
https://code.google.com/p/ibm-db/issues/detail?id=158
Co-Authored-By: Rahul Priyadarshi <rahul.priyadarshi@in.ibm.com>
Change-Id: I0f06f6314c382e83573d762abe5981db0a02a83a
Diffstat (limited to 'requirements.txt')
0 files changed, 0 insertions, 0 deletions