Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of bpendleton.derby@gmail.com
 designates 209.85.214.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=JLSa+9JiWQTxw1ueNhLGujFNpK6I94sREEAWf2X0A0lNg8TvMNkXhVYv/TI7xlTelM
         tFK/q0y1YrICkFpUmpY8yU3I2rVgxduL2IGL9yfiGlc23enc9yCcs/pYXoXAurnmf+du
         Zk2otkOADngcxs1csTDd3H8kV2ETapwsCFcTQ=
Message-ID: <4D02FD9A.1010308@gmail.com>
Date: Fri, 10 Dec 2010 20:27:06 -0800
From: Bryan Pendleton <bpendleton.derby@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: productizing the metadata wrapper functions
References: <4D02676B.30302@oracle.com>
In-Reply-To: <4D02676B.30302@oracle.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> These wrapper functions let you use SQL to examine
> database, ResultSet, and parameter metadata.

The database metadata table function seems quite natural and powerful.

I'm less clear on how to use the RS and Parameter functions; I looked
at the examples in DERBY-4926 and DERBY-4927 but they seemed pretty
artificial. Do you have more substantial examples? Also, would these
latter two functions be useful in a JDBC program? Or are they something
that would mostly be useful in IJ?

I guess what I'm asking is: could I somehow pass an actual ResultSet
object or PreparedStatement object to one of these functions? Or do
they always have to take a query string and compile it themselves?

Lastly, why does it take several seconds to register these functions?
Is it due to how they are packaged? (That is, if they were embedded
in derby.jar would the registration go faster?) I'm a bit surprised
that something as seemingly trivial as registering three table
functions could take that much time.

Anyway, thanks very much for doing this work, and for advancing the
proposal; it's quite interesting and I've been learning a lot by
reading your work and following the discussions!

bryan