Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <46EEAE33.5020903@apache.org>
Date: Mon, 17 Sep 2007 09:41:23 -0700
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Updated: (DERBY-3069) Derby does not resolve functions
 bound to methods with varargs.
References: <27608581.1190033876519.JavaMail.jira@brutus>
In-Reply-To: <27608581.1190033876519.JavaMail.jira@brutus>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


> Rick Hillegas updated DERBY-3069:
> ---------------------------------

>> Derby does not resolve functions bound to methods with varargs.
>> ---------------------------------------------------------------

Jira's down so sending this comment as e-mail:

Is there going to be some write up on exactly how the proposed method 
resolution will work with varargs, so that people can review it and see 
if it conflicts with the standard method resolution?

Will this be a different PARAMETER STYLE (than JAVA)? If not what does 
it say about Derby's commitment to standards when a SQL routine resolves 
to a method in Derby that it would not resolve to on another database 
that is following the SQL standard?

Dan.