I'm working with a small team doing a Proof of Concept at a customer location. We're looking at iBATIS as a DAO solution however we have many stored procedures that return upwards of 10k rows. Our previous solution cut the number of rows returned to a fixed limit.
Is there any way to do this using iBATIS currently? Since we have no handle to the statement, I'm at a loss right now. Any help would be greatly appreciated. Thanks Clinton Begin wrote: > > No, it doesn't call setMaxRows. Probably a legacy decision for driver > compatibility reasons, but I suppose we're well past that now. If you > think > it will improve performance for you, we can probably add it. If so, > please > open a JIRA ticket for it. > > Clinton > > On 5/10/07, BenBaril <[EMAIL PROTECTED]> wrote: >> >> >> I'm wondering on how the implementation of maxRows works when calling >> queryForList. Does it execute a stmt.setMaxRows(maxRows); or does it >> receive >> all the rows from the database, parse then trim? >> >> Thanks, >> Benjamin Baril >> -- >> View this message in context: >> http://www.nabble.com/QueryForList-%3A-How-does-maxRows-work--tf3722314.html#a10415657 >> Sent from the iBATIS - User - Java mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/QueryForList-%3A-How-does-maxRows-work--tf3722314.html#a10417487 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
