>From a strictly technical point of view, your suggestion makes perfect sense, although you should probably use the standard term "derived table" or "inline view" instead of "nested join". The problem is that the specs/docs already have some things to say about this:
http://nhforge.org/doc/nh/en/index.html#mapping-declaration-join However, if the use of derived tables is restricted to related entities, it will comply with the docs and still behave more properly. In other words: select [same stuff here] from A a inner join APrime ap on a.Id=ap.Id left outer join (select .... from b inner join BPrime bp on b.Id=bp.Id) db on A.Id = db.Id The place to start would be the AbstractEntityPersister /G 2011/10/3 Isaac Cambron <[email protected]> > Anyone have any thoughts on this? I'd appreciate a bit of feedback before I > pour a few days of dev work into this... > > > On Tue, Sep 27, 2011 at 9:44 PM, Isaac Cambron <[email protected]> wrote: > >> I'd very much like to patch >> NH-2900<https://nhibernate.jira.com/browse/NH-2900>, >> but since it'll only be my second patch, I figured I'd ask about before I >> dive in: >> >> 1. Since I just filed it, does it make sense? >> 2. If I patched this, would it be accepted? >> 3. Any pointers one where I should start? I know my way around the code >> base a little bit, but if anyone has some advice on how to attack this >> issue, I'd appreciate it. >> >> Thanks, >> Isaac >> > >
