I agree with Martin. In my company we use iBatis and we appreciate both result mapping and dynamic SQL features, but sometimes we only need dynamic SQL with direct access to the underlying jdbc cursor. For instance... we use JasperReports for report generation (and dynamic queries are very useful with reports), but we cannot use iBatis because we have memory issues (and bad performances) for large reports; it would be nice if we could call a dynamic query and pass the underlying jdbc resultset to JasperReports.
Davide. -----Messaggio originale----- Da: Martin Ellis [mailto:ellis....@gmail.com] Inviato: giovedì 18 febbraio 2010 19.27 A: user-java@ibatis.apache.org Oggetto: Re: read large result set in Ibatis3 > On 2/18/2010 10:16 AM, Tomáš Procházka wrote: >> Ideal will be possibility to add method to mapper will return object >> on which I can call something like getNext(), hasNext() and close(). On 18 February 2010 17:44, Guy Rouillier <guyr-...@burntmail.com> wrote: > That is very JDBC-ish. From my perspective, iBATIS attempts to hide > all that so that the programmer can just deal with lists of objects. > ResultHandler lets you change how the list gets built. What you are > asking is for JDBC to be exposed again, something like > ResultSetHandler. I guess it would be possible to make that > pluggable, but then you are undoing much of the framework. Only the result handling side of the framework. You'd still have the dynamic SQL, and parameter handling without it. That in itself is probably enough incentive to use iBATIS. 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
