Closed jalchr closed 13 years ago
I think might not be that descriptive thou ... you might want to rename this operation ... but its helpful and I use it frequently
Also all the projects miss the "AssemblyInfo.cs" file ... I think this has to do with the build script ... but they should not be referenced by the project files ...
That's jalchr! I didn't merge this in because I went a slightly different direction with it. But the functionality is there now. I'll try and publish out a nuget package later today. Now each join operation can accept pipeline input for the left option (Join and NestedJoin)
Very well, I trust you made some improvements, I'll check it later.
Did you add the functionality of the "Multi-Join" commits ? What I did there was using the "join" way of JoinOperations into "Nested-Join", so we get same performance even on multiple column levels, for example I have 2 columns to join on, Id and email ... I want to "inner Join" on Id and "Left Join" on the email ... This was only possible with "Nested-Joins" which is very slow. I didn't look at your changes yet , so I'm just asking ...
Added RightJoinWithOperation where the input of a join operation can be the output of a previous operation or branching
Solves this https://groups.google.com/forum/?fromgroups#!topic/rhino-tools-dev/_iXETiN-gQ8