×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu, Mar 12, 2015 at 10:05 AM, <rob@xxxxxxxxx> wrote:
The common problem is your "where" clause. Let's say your table has
1,000,000 rows. Your "where" clause returns only 1,000 rows. When ran on
the host you notice nothing. However, when ran on a client it still has
to pass each row down to the client for analysis. HUGE difference.
You're implying that the WHERE clause is executed on the client, while
the rest of the SQL statement is executed on the server? That is what
it sounds like, especially if you are suggesting to bundle up the
result set as an Excel file on the server and then downloading the
Excel file to the client.
I may be naive, but I don't think that's how it works. I think Vern's
explanation (that STRSQL on the server is free to fetch roughly a
screenful of rows at a time and stop after the first screen, while
client software may be waiting for the entire result set) is much more
plausible.
John Y.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
