> Also, the JasperReports example mentioned earlier in the thread could be part of a > batch process for all we know. > The point is: not every application is a web application.
You're right. We have no problem using iBatis on the web part of our application because usually on the "interactive" side you have to read a small amount of records for each query (and in this case the advantage of automatic result mapping is amazing!). But on the "batch" side often you HAVE to manipulate directly jdbc cursors to avoid memory and performance issues so, in my opinion, it would be nice if iBatis could have a way to use the power of dynamic queries, bypassing only automatic result mapping by exposing directly the jdbc cursor. Davide. -----Messaggio originale----- Da: Martin Ellis [mailto:ellis....@gmail.com] Inviato: giovedì 25 febbraio 2010 12.00 A: user-java@ibatis.apache.org Oggetto: Re: read large result set in Ibatis3 On 25 February 2010 10:53, zkn <z...@abv.bg> wrote: > I use limit and offset exactly for this purpose. I think it's much > better for the application and the database server to get the total > count with one query and then just get the page you actually need and > want to show to the user. You don't really need to show 10K rows on a > single page to user, do you? Giovanni is talking about web services, not web pages. Also, the JasperReports example mentioned earlier in the thread could be part of a batch process for all we know. The point is: not every application is a web application. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: user-java-unsubscr...@ibatis.apache.org For additional commands, e-mail: user-java-h...@ibatis.apache.org
