"foreignkey" is out. dont use it at all. "remote_side", when the "remote side" of the relationship is ambiguous based on the join condition, i.e. a self referential mapping relationship. can be provided for otherwise non-ambiguous cases as well.
"foreign_keys", when your join condition contains comparisons where neither side of the comparison is a foreign key column. if you want to provide it unconditionally, its just a list of all Columns that have a ForeignKey. but i dont think youd need it in any of your cases since your joins correspond to the foreign key relationships of your tables. On Feb 20, 11:03 am, svilen <[EMAIL PROTECTED]> wrote: > > using the "foreignkey" parameter > > which is both deprecated and also more or less mutually exclusive > > with "remote_side". > > how do u mean mutualy exclusive - so i don't need to specify that > foreign*key* stuff if i do specify remote_side? > or there are cases where it is needed? > i'll try.. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
