commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Caswell" <>
Subject RE: [dbutils] ResultSetMetaDataHandler
Date Tue, 21 Oct 2003 23:49:08 GMT
The idea behind the ResultSetMetaDataHandler is to allow a caller to get to
the result set metadata without actually having access to the result set,
such as when the result set is being consumed and passed back in some other
form. For example, looking at the DbUtils class, the executeListQuery
consumes the result set. There is no easy way for the caller to get access
to the metadata except through the handler.

Steven Caswell
Sun Certified Java Programmer
a.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."

> -----Original Message-----
> From: David Graham [] 
> Sent: Tuesday, October 21, 2003 9:55 AM
> To:
> Subject: [dbutils] ResultSetMetaDataHandler
> I'm having trouble thinking of a use case that supports the 
> need for the ResultSetMetaDataHandler interface.  I view meta 
> data handling as part of handling a ResultSet so it can be 
> done in a ResultSetHandler.  Because ResultSetHandler can 
> call rs.getMetaData(), I don't see a need for a separate 
> interface and the additions of methods to QueryRunner to support it.
> This is an effort to simplify the dbutils API; I don't think 
> ResultSetMetaDataHandler is pulling it's weight.
> If no one is opposed, I'll remove ResultSetMetaDataHandler tommorrow.
> David
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message