Re: Paging large database result sets

[Javier Borrajo]

Not to take away from PCA (GS/J can no doubt cache big results sets, etc...), however, in a case where the result set is that big, I would probably not do that. No silver bullets if the result set is this huge. Better to return a subset in the first invocation of the query, and then on the next invocation return the next chunk etc... It's not elegant but for something of this scale it is more practical. Or prompt the user for a more practical filter! What the heck is the client going to do with a 100,000 records anyway? !!! This is exactly what we do.   There is no need to not allowing the user to not making querys that return 100.000+ records. The trick is to tell the user, hey, there are 123,456 records fitting this query and here you have the first 40 records, and you may scroll down the JList to get more, but probably you may prefer to refine your query, don't you?   Regards       Javier