snip
>
> Ah, but the whole point of this enhancement is that it's unperformant to
> use RowProcessor#toBean on each row; it's much faster to call
> RowProcessor#toBeanList once. So there's no such thing as an
> OptimizedBeanRowHandler; the optimization is to not use a RowHandler!
>
/snip
I'd pus
Liam Coughlin wrote:
On Tue, Feb 10, 2009 at 2:32 AM, Dan Fabulich wrote:
1) OptimalBeanListHandler
Ideally, these classes should be split up more. There shouldn't really be a
BeanListHandler, just a ListHandler which takes a RowHandler on
construction, and then you can just use the approp
On Tue, Feb 10, 2009 at 2:32 AM, Dan Fabulich wrote:
> 1) OptimalBeanListHandler
>
> http://issues.apache.org/jira/browse/DBUTILS-37
> This bug provides a patch that considerably improves the performance of
> BeanListHandler.
>
> However, Julien correctly points out that:
>
>> With the change I p
I had some questions about a few remaining bugs... maybe somebody here can
help...
1) OptimalBeanListHandler
http://issues.apache.org/jira/browse/DBUTILS-37
This bug provides a patch that considerably improves the performance of
BeanListHandler.
However, Julien correctly points out that:
W
