One other note. I will be perfectly happy if we just make the
mapColumnsToProperties() method protected. But I think it would be even
better if we made it a public method in the ColumnProcessor interface.
That way, the ColumnProcessor would completely encapsulate the mapping of
both names and data
I am finding that my DAOs that use the BeanHandler are ending up with a lot
of code like this:
String queryName = "select column1 as beanProp1, column2 as beanProp2,
column3 as beanProp3"
This gets to be very redundant and clunky for large rows, and it happens
because DbUtils assumes that the
OK, be gentle if I have messed anything up here, I am new to Bugzilla.
I have submitted the patch as a source diff per David's request. The
enhancement is logged as Bug 24997.
Per Yoav's request, I have implemented an interface that enables pluggable
conversion strategies. The interface is Column
Hi, first off I'd like to say thanks for the DbUtils package. It has been
very helpful for cleaning up my code in places where I have to do manual
persistence.
I have had to modify the code in order to use the BeanHandler, and I wanted
to offer my modifications as a patch to the codebase.
Let me
