Hi Johann, hi Ricky,
Thanks for reaching out to the mailing list before taking action!
I do also prefer option c.
In principle, all inner join strategies can also be applied for all outer
joins (for some hash strategies, a special HashTable implementation is
required).
I propose to add two method
Hi Johann,
I'd prefer 1.c, because the different join variants are semantically
different and this should be IMO reflected in the API. Moreover, the
`JoinHints` are used to give hints for the selection of the underlying
strategy for the different join variants. For `leftOuterJoin` you could
either
