search

qizhiyi / sqlalchemy-migrate

Automatically exported from code.google.com/p/sqlalchemy-migrate
MIT License
0 stars 0 forks source link

SQLAlchemy foreign key constraints end up referencing "migration_tmp" #137

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create two tables in a database, one of which has a foreign key to the other 
table
2. Create a migration that modifies the table the foreign key constraint is 
pointing to

What is the expected output? What do you see instead?
The foreign key constraint should point to the original table name. Instead it 
now references "migration_tmp"

What version of the product are you using? On what operating system?
Python 2.6, SQLAlchemy 0.7.3, SQLAlchemy-migrate 0.7.2

Please provide any additional information below.

Original issue reported on code.google.com by kamil.ki...@gmail.com on 19 Nov 2011 at 1:01