Table.copy should always consider key rather than name
Issue #2643
resolved
When copying a primary key column that is also a foreign key using tometadata, if the foreign key column specifies a key instead of defaulting to the name then sqlalchemy can't determine the column that is foreign keyed.
Comments (4)
-
reporter
-
repo owner
- changed milestone to 0.8.0final
- assigned issue to
- changed component to schema
looks good...
add tests to test/sql/test_metadata.py and backport to 0.7.10
-
repo owner
- changed status to resolved
e26b28224d7c1745a8a2892372e1f5a8862e792c (0.8)
027eda4a34352ff8525119d841f06c73236e9723 (0.7)
thanks for the fix !
-
repo owner
- removed milestone
Removing milestone: 0.8.0final (automated comment)
- Log in to comment
Replying to richardmurri:
I suppose I should mention that this happens both on 0.7.9 and 0.8.0beta2