On Fri, Oct 23, 2009 at 12:17 AM, Schuh, Richard <[email protected]> wrote:
> Now a question for those more deeply involved in Pipelines than me, is there > any advantage, other than perceived beauty, of using the "not pick wn == > ,XX," construct vs. "pick wn ^== ,XX,"? I would think not, but I may be > wrong. The two would both do the same comparison and send the records down > the same streams. I can see the advantage of having a visually simpler pipe > by using "not lookup autoadd" when only the records that become the masters > are wanted. To me the advantage is that I can remember "not" better than the trigraph for the "not equal" operator. But "not" is more than just syntactical sugar, but really is another pipeline stage that gets dispatched etc. So there is a small cost involved in passing the records through it. Depending on how trivial the subject stage is, the overhead becomes more visible. I suspect that "not cms" will be less of an issue, but I try very hard to get rid of my habit to use "not chop" :-) This does not apply to using "nlocate" vs "locate" to avoid messing with the secondary output. Only "not locate" would be more expensive than "nlocate" Rob
