Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; charset=iso-8859-1
Date: Tue, 15 Sep 2009 10:27:33 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: Accent-insensitive searches
In-reply-to: <25433944.post@talk.nabble.com>
Sender: Knut.Hatlen@Sun.COM
To: Derby Discussion <derby-user@db.apache.org>
Message-id: <wjo8pr9svci2.fsf@sun.com>
Organization: Sun Microsystems
References: <25362254.post@talk.nabble.com> <25433944.post@talk.nabble.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (usg-unix-v)

josu <josu.eh.mondo@gmail.com> writes:
> Knut Anders Hatlen wrote:
>> 
>> You can verify that the database was created with the correct territory 
>> and collation by evaluating this in IJ and see that "TERRITORY_BASED" is 
>> returned: 
>> ...
>> And also check that service.properties in the database directory 
>> contains the following line: 
>>  
>> derby.serviceLocale=es_ES_accentinsensitive 
>> 
>
> I checked both, and they're ok. But the result of the queries is still
> accent-sensitive. I'm working with Windows XP and it seems you're working
> with Linux, could that be the reason of the different behaviour?

Maybe. I've only tried it on Solaris, and I don't know if there are any
differences on other platforms.

To check that the Java VM picks up your collator correctly, you could
try this code and see what it prints:

    Locale locale = new Locale("es", "ES", "accentinsensitive");
    Collator c = Collator.getInstance(locale);
    System.out.println(c.compare("electrico", "el�ctrico"));

"0" should be printed if your custom collator has been correctly
installed.

-- 
Knut Anders