>I would suggest using stored procedures to get exactly the number of row >you want. Transferring more data than you need in a query takes time as >mentioned in earlier replies from everyone. Other issues are related to >connection pooling and scalability. If you're query returns several >hundred or thousand rows, the query itself is fairly quick in a DB like >oracle, but you're using the connection for a longer duration. If the >website is only serving a few concurrent connections you're fine. On the >otherhand, if you're serving hundreds of connections per second, getting >800 rows to only show 20 will likely result in timeouts.
That may all be true, but I was asking about the actual way that JSTL behaves, not about higher level application designn. > >I don't know mysql, but another thing to consider. > >peter -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
