S
ske
Guest
> ...I had tried to start a discussion about the possibility of allowing us > access to a "DataServer for Progress SQL" ... It seems to me that this > might be a path towards having server-side joins in our client-server >code (ABL-to-OE). Some years ago, I think the standard answer to such problems would have been to use a local AppServer on the database server machine (or close to it over high-speed LAN) with pre-programmed procedures to perform all complex queries (both joins or any kind of complex data processing), and then return the data to the client. That removes the inefficient network traffic for executing remote database queries over multiple tables from ABL. (Maybe it is still the answer.) I'm guessing that remote access from clients directly to the database for complex queries may not have been so common, since those would usually have been implemented via an AppServer, and that way most direct database access from ABL did have access to shared-memory access or at least high-speed network access, and thus Progress did not prioritize (or were able to hold off) optimizing remote database access within ABL queries.
Continue reading...
Continue reading...