Comment 1 for bug 1186353

I fixed a similar problem for DB2.

I looked up the constraint name... it was in the table structure.

Sqlalchemy did know the name of the constraint, but it just didn't use that name when dropping.

Here's the interesting bit: [fk.name for fk in table.constraints if column.name in fk.columns]