A
alex.wiese.pulse
Guest
[quote user="frank.meulblok"] A key point here is that buffer state outside a FOR FIRST loop is *undefined* (see Progress KB - State of buffer outside of FOR FIRST loop is undefined ). Which means you really shouldn't relied upon. With client-side joins, the client reads the left-hand side first, then fail to find a record on right-hand side, and the 1st record lingers around in the buffer due to black magic implementation details even though the inner join fell through. With server-side joins, the client isn't aware of anything until the server returns. The server gets the query, finds the left-hand side record, fails to find a record on right-hand side, and returns nothing to the client. Because that's what's expected of an inner-join query if one side of the join has no data. Make the query an OUTER-JOIN query and chances are it'll also work with server-side joins. Or not, because on the client you're still checking the buffers outside the loop, thus the state of the buffers still is undefined. [/quote] Yeah that makes sense. I guess we have a lot of code to refactor [:'(]
Continue reading...
Continue reading...