Sorry no time to write testcases for that, maybe later. 1) When defining a primaryjoin and a secondaryjoin for a relation property, not giving in the intermediate table triggers an exception.
2) Defining a mapper on a custom join, and adding a relation property to that mapper to another mapper, it seems as if the custom join criteria is ignored and only the table of the select is regarded. 3) An extended secondaryjoin where the column names are longer then the permittable limit doesn't translate the column names as the colspec of the select aliases them. ------------------------------------------------------- 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
