D
dbeavon
Guest
Brian, thanks for the tip. I was worried that the article, even if I found it, would not be relevant to remote client/server connectivity... But it appears to be fairly relevant. Here it is: Progress KB - OpenEdge 4GL Query concepts (FOR EACH, FIND, GET, INDEX) Here is an interesting part related to resolving WHERE conditions. A version 7 server is capable of doing most selections, and sends only those records which fully satisfy the query to the client.It is important to note that there are some selection operations that the server cannot do, either because they require access to program variables in the client, or because they are not implemented on the server (the most important such function is CAN-FIND which is not yet implemented on the server). In such a case, the server sends the records to the client along with an indication that it cannot perform the selection, and the client must do it. My understanding is that the only "WHERE" conditions that a server is able to resolve entirely on the server-side are conditions that use *indexed* fields. However the statement above does not explicitly say that. It leads us to believe that the server may do better than that. I was hoping that I could find a better explanation than this of which types of WHERE conditions would be resolved on the server, during a FOR EACH scan of a single table.
Continue reading...
Continue reading...