On Apr 26, 2014, at 2:23 PM, Michael Bayer <mike...@zzzcomputing.com> wrote:
> If OTOH you do in fact want this query to take the current Company.id into > account, this would be simple using primaryjoin/secondaryjoin/secondary, it > just requires that the IN is unwrapped into a regular join criterion. Assume > the name of the CompaniesUsers table is "companies users": sorry, this is an editing problem, this sentence should read: If OTOH you want a full blown relationship(), which grants the ability to automatically compose this join condition into a larger query as well as eager loading, this would be simple.... (rest of sentence follows) -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
