Michael, Thanks.
It was reflecting fine, it's just that nobody ever put the foreign key constraints into the DDL (what would MySQL do with them anyway). I solved my problem by just using relation(OtherTableObject, primaryjoin=ThisTableObject.c.id == OtherTableObject.c.id) When I use append_item(ForeignKey()) twice on the same column object, relation() says sqlalchemy.exceptions.ArgumentError: Error determining primary and/or secondary join On 9/21/06, Michael Bayer <[EMAIL PROTECTED]> wrote: > foreign keys should be reflected (if thats what youre asking). if > you have a mysql table thats not reflecting properly, feel free to > send its DDL on over. > > if you want a column to be a foreign key to several other tables, > youre better off appending ForeignKeyConstraint objects to the end of > your Table definition. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
