Issue Details (XML | Word | Printable)

Key: DBUTILS-37
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Dan Fabulich
Reporter: Julien Aymé
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Commons DbUtils

BeanListHandler#handle(ResultSet) is not optimal

Created: 09/May/07 10:50 AM   Updated: 07/Mar/09 06:09 AM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Time Tracking:
Not Specified

File Attachments:
  Size
Java Source File Licensed for inclusion in ASF works OptimalBeanListHandler.java 2007-05-09 11:07 AM Julien Aymé 3 kB
Text File Licensed for inclusion in ASF works OptimalBeanListHandler.patch 2007-05-09 11:07 AM Julien Aymé 2 kB

Resolution Date: 25/Feb/09 10:06 AM


 Description  « Hide
I use the BeanListHandler for huge ResultSets (about 1000000 rows), and I searched through the code to see if I could gain little time.

It appeared to me that the following code - in BeanProcessor.class - was executed too many times:

PropertyDescriptor[] props = this.propertyDescriptors(type);
        ResultSetMetaData rsmd = rs.getMetaData();
        int[] columnToProperty = this.mapColumnsToProperties(rsmd, props);

for the following reason.
Since BeanListHandler extends GenericListHandler, the method #handle(ResultSet) calls #handleRow(ResultSet) for each row in the ResultSet,
which in the case of a BeanListHandler, calls RowProcessor#toBean(ResultSet, Class),
which itself calls BeanProcessor#toBean(ResultSet, Class).

A very simple way to make the BeanListHandler#handle(ResultSet) method faster is to override the GenericListHandler#handle(ResultSet) method by this code:

public Object handle(ResultSet rs) throws SQLException {
        return this.convert.toBeanList(rs, type);
    }

This way, the code I showed would be called only once, as it would not call BeanProcessor#toBean(ResultSet, Class) for each row but BeanProcessor#toBeanList(ResultSet, Class).



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.