Michael Bayer wrote:
i suppose the advantage over a separate primary key / foreign key in the child table is that it enforces a one-to-one mapping ?
Yep - it's one of the things I really like in SA c.f. SQLObject which forced you to use internal primary keys (or at least it did, haven't checked recently - no need). I like my entities to use and enforce their natural relationships (leveraging the full power of the backend rdbms as much as possible).
Robert ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
