db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lance J. Andersen" <Lance.Ander...@Sun.COM>
Subject Re: Returning an empty result set
Date Thu, 02 Feb 2006 20:36:41 GMT

David W. Van Couvering wrote:

> According to our most esteemed spec lead, for the new metadata calls
> that return a result set, if we don't support the metadata call, we
> should return an empty result set.
> Can anyone provide me some guidance as to the best way to do this?  The
> constructor for org.apache.derby.client.am.ResultSet requires a lot of
> parameters that I don't want to try and create, and the same is true for
> the engine.
> And a question to Lance: does it really make sense for getSchemas() and
> getClientInfoProperties() to return an empty result set, isn't that a
> bit misleading?
Hi Dave,

There is already a precedent for this type of behavior. getUDTS(), 
getSuperTypes() are an example

(your friendly neighborhood spec lead....)

> Thanks,
> David

View raw message