Thank you, that is exactly what I needed. For the record, it also works with primaryjoin defined on the ColumnProperties (Table2.code etc...) and with a column property.
> I'm not sure which side here you'd want to consider "foreign", that is, the > column which seeks to match an existing column. Switching "foreign_keys" to > point to table1.c.code or table2.c.code will cause relationship to consider > it as many-to-one, or one-to-many, respectively. If my relationship has no backref, and the viewonly flag is set to false, what are the implications of switching foreign_keys ? Regards, -- Ronan Dunklau -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
