I just noticed this comment thats been sitting on the wiki for a few months:
If using autoload=True when defining your metadata, be sure your FK constraint names are unique to the schema . PostgreSQL scopes FK constraint names to the table, but SQLAlchemy loads them from the SQL standard information_schema, which is designed for schema-scoped constraint names. which is news to me; the query used to reflect foreign keys takes table name into account, and a unit test which reflects anonymously- created foreign keys from two different tables works fine (and always has...). can someone illustrate this problem for me ? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
