I don't know if Steve's still reading this list, but if I recall correctly,
he remarked that group-join isn't supported yet, and he doesn't know whether
it will be in RTM.
DefaultIfEmpty and groupjoin are a massive undertaking, although it seems
they are easy at first. It's a major pain in the you-know-where to support
these, especially in the more advanced scenarios. The main gripe is that a
groupjoin's seen as 1 side of another join and acts like it and
defaultifempty fulfills the role of the other side of the join and refers to
the other side of the groupjoin. So this is _2_ joins which should be _1_.
It's also a nightmare, alias-wise, as defaultifempty is seen as a set, but
as it refers to a part of a groupjoin elsewhere in the tree, you have to
COPY the side of the groupjoin and re-alias the thing, also re-aliasing the
parts which refer to THAT. Not sure if the re-linq people have solved this
in re-linq.
I.o.w.: the person who will pick this up and implement it, has to love S&M
and has to have a chronical sleep disorder as you wont be having a lot of
free time to do anything else ;)
FB
> Now that Alpha versions of NH3 are being put on the web, I was wondering
> when support for DefaultIfEmpty for outer joins is going to be integrated.
>
> I see that NHibernate/Linq/GroupJoin/
> NonAggregatingGroupJoinRewriter.cs did not receive any updates for the
past
> nine months and it specifically does not support DefaultIfEmpty
> (NotSupportedException). Also, the DLinqJoin7 test case in /
> NHibernate.Test/Linq/LinqQuerySamples.cs which tests this construct is set
> to [Ignore] and I cannot find a JIRA issue on this.
