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: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Date: Mon, 30 Nov 2009 08:41:44 -0800
From: Rick Hillegas <Richard.Hillegas@Sun.COM>
Subject: Re: Regarding Stored Procedures
In-reply-to: <22b99aa10911250050p6cd2b06bl13616b47f00c94bc@mail.gmail.com>
Sender: Richard.Hillegas@Sun.COM
To: derby-dev@db.apache.org
Message-id: <4B13F5C8.9010509@sun.com>
References: <22b99aa10911250050p6cd2b06bl13616b47f00c94bc@mail.gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)

Hi Shazin,

Compilation for these method calls is handled by StaticMethodCallNode. 
StaticMethodCallNode.generateExpression() generates the byte code needed 
to invoke the user-defined routine at execution time.

If you are interested in puzzling through the details, I recommend 
viewing the abstract syntax trees in xml, as shown on DERBY-4415. This 
will help you see what classes are involved during compilation.

The main execution-time class is a generated class, which Derby creates 
during compilation. If you want to examine the generated class, follow 
the instructions here: http://wiki.apache.org/db-derby/DumpClassFile

Hope this helps,
-Rick

Shazin Sadakath wrote:
> Hi All,
>
> Can anyone tell me what happens and what are the classes associated with
> below SQL Command send via a JDBC statement to Derby Engine.
>
> Statement 1
> "CALL XXX()"
>
> Statement 2
> "VALUES YYY()"
>
> XXX() is a Procedure
> YYY() is a Function
>
> Thanks in advance,
> Shazin