Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <855750032.1103387725457.JavaMail.apache@nagoya>
Date: Sat, 18 Dec 2004 08:35:25 -0800 (PST)
From: "Jeremy Boynes (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-89) Support Java Signature in procedure
 declaration
In-Reply-To: <1750138883.1102296080816.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://nagoya.apache.org/jira/browse/DERBY-89?page=comments#action_56842 ]
     
Jeremy Boynes commented on DERBY-89:
------------------------------------

I applied the patch to a fresh checkout and it built OK. The method being referenced is included in the patch (starting at line 177). Could you have had an patching ClassInspector.java?

> Support Java Signature in procedure declaration
> -----------------------------------------------
>
>          Key: DERBY-89
>          URL: http://nagoya.apache.org/jira/browse/DERBY-89
>      Project: Derby
>         Type: New Feature
>   Components: SQL
>     Reporter: Jeremy Boynes
>  Attachments: derby_java_signature.patch
>
> Derby cannot resolve procedures to methods when the Java signature determined from the SQL declaration is ambiguous. SQL-03 Part 13 allows a Java signature to be supplied in the SQL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira