Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <450EC9F4.4050007@apache.org>
Date: Mon, 18 Sep 2006 09:31:48 -0700
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [jira] Updated: (DERBY-1862) Simple hash improves performance
References: <15758740.1158581063178.JavaMail.jira@brutus>
 <450E9F20.2090304@sun.com> <wjo8slip6t2u.fsf@sun.com>
In-Reply-To: <wjo8slip6t2u.fsf@sun.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Knut Anders Hatlen wrote:

> �ystein Gr�vlen <Oystein.Grovlen@Sun.COM> writes:
> 
> 
>>Andreas Korneliussen (JIRA) wrote:
>>
>>
>>>String.toUpperCase(..) with english locale, should return a string
>>>with the same number of characters, and it should therefore be valid
>>>to do a check of number of characters before doing any conversions.
>>
>>Is it correct to always use English locale in this case?  Ref the
>>reference guide on SQL identifiers:
> 
> 
> And is it correct to upcase the identifiers before comparing them in
> findColumnName()?

I beloive so, based upon this test in the javadoc of ResultSet.

"Column names used as input to getter methods are case insensitive. When
a getter method is called with a column name and several columns have
the same name, the value of the first matching column will be returned."

Dan.