×
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.
Any DB file with that many records is going to take forever to
processes.
I've got to disagree. On a properly sized machine (won't be running 2.1B
rows on a 515) with the right indices you should get results back in
several ms.
I think that instead of modifying your RPG code you
should take a look at reworking your java code so that you can have
multiple users.
That's against "proper" web design. The web is stateless, to try to pair
a specific client to a specific server-job is against the "rules."
There's no reason you can't share that connection, you just have to be
smarter about how you page the results.
With proper SQL and cooperation from the app you can get paging
performance to be independent of the page# you're on. This was discussed
last year sometime on the list (don't recall whether it was this one of
Web, or Midrange)
Having said that, I don't see why the change was made initially away
from returning all the rows. I'm assuming (dangerous, I know) that we're
not talking about 10s of 1000s of rows here, but perhaps 300 per client?
Maybe 1000. Should have been ok on one request, but I don't know the
app.
-Walden
midrange.com
