You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by David Graham <gr...@yahoo.com> on 2003/10/21 16:55:00 UTC
[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
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [dbutils] ResultSetMetaDataHandler
Posted by Juozas Baliuka <ba...@centras.lt>.
remove it.
----- Original Message -----
From: "David Graham" <gr...@yahoo.com>
To: <co...@jakarta.apache.org>
Sent: Tuesday, October 21, 2003 5:55 PM
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
> http://shopping.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [dbutils] ResultSetMetaDataHandler
Posted by Steven Caswell <st...@mungoknotwise.com>.
I was looking at an older version and didn't remember these methods had been
removed. Beyond these, there is no other need for the handler. Dumping it is fine.
Quoting David Graham <gr...@yahoo.com>:
> --- Steven Caswell <st...@mungoknotwise.com> wrote:
> > 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.
>
> The new code does not contain methods like executeListQuery that don't
> accept a ResultSetHandler. I still don't see a need for
> ResultSetMetaDataHandler since all the methods take a ResultSetHandler
> which has access to the meta data.
>
> David
>
> >
> >
> > Steven Caswell
> > Sun Certified Java Programmer
> > steve@mungoknotwise.com
> > a.k.a Mungo Knotwise of Michel Delving
> > "One ring to rule them all, one ring to find them..."
> >
> >
> > > -----Original Message-----
> > > From: David Graham [mailto:grahamdavid1980@yahoo.com]
> > > Sent: Tuesday, October 21, 2003 9:55 AM
> > > To: commons-dev@jakarta.apache.org
> > > 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
> > http://shopping.yahoo.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Steven Caswell
(Hobbit name Mungo Knotwise of Michel Delving)
steve@mungoknotwise.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [dbutils] ResultSetMetaDataHandler
Posted by David Graham <gr...@yahoo.com>.
--- Steven Caswell <st...@mungoknotwise.com> wrote:
> 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.
The new code does not contain methods like executeListQuery that don't
accept a ResultSetHandler. I still don't see a need for
ResultSetMetaDataHandler since all the methods take a ResultSetHandler
which has access to the meta data.
David
>
>
> Steven Caswell
> Sun Certified Java Programmer
> steve@mungoknotwise.com
> a.k.a Mungo Knotwise of Michel Delving
> "One ring to rule them all, one ring to find them..."
>
>
> > -----Original Message-----
> > From: David Graham [mailto:grahamdavid1980@yahoo.com]
> > Sent: Tuesday, October 21, 2003 9:55 AM
> > To: commons-dev@jakarta.apache.org
> > 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
> http://shopping.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [dbutils] ResultSetMetaDataHandler
Posted by Steven Caswell <st...@mungoknotwise.com>.
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
steve@mungoknotwise.com
a.k.a Mungo Knotwise of Michel Delving
"One ring to rule them all, one ring to find them..."
> -----Original Message-----
> From: David Graham [mailto:grahamdavid1980@yahoo.com]
> Sent: Tuesday, October 21, 2003 9:55 AM
> To: commons-dev@jakarta.apache.org
> 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
http://shopping.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org