db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Ostgaard <Vemund.Ostga...@Sun.COM>
Subject Re: Setting collation=TERRITORY_BASED when territory is set to an unsupported locale
Date Tue, 15 Jan 2008 15:07:29 GMT
Thank you for sharing your opinions, Knut and Mamta. I''ve reported this 
in Jira as DERBY-3320.


Mamta Satoor wrote:
> I think that we should fail at both database creation time and boot
> time if the requested locale can not be found when collation is
> territory based.
> Mamta
> On 1/14/08, Knut Anders Hatlen <Knut.Hatlen@sun.com> wrote:
>> Vemund Ostgaard <Vemund.Ostgaard@Sun.COM> writes:
>>> So, should database creation/boot fail if the collation is territory
>>> based and the locale is not supported?
>> That sounds reasonable to me. If the Java runtime silently uses en_US
>> collators when the database's territory is something different, I think
>> we can see a variety of problems if the database is moved between
>> systems that support collators for the database's territory and systems
>> that don't. For instance, the index entries may appear to be unordered
>> and queries that use indices may give strange results.
>> I think at least database boot should fail when collation is territory
>> based and locale isn't supported. For database creation we could
>> alternatively detect that the situation has occurred, change the
>> collation to UCS_BASIC before the database is created, and add a warning
>> explaining what has happened. But I think failing is the best option for
>> creation too.
>> --
>> Knut Anders

View raw message