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

regards
lance
(your friendly neighborhood spec lead....)

Thanks,

David

Reply via email to