Thank you for sharing your opinions, Knut and Mamta. I''ve reported this
in Jira as DERBY-3320.
Vemund
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 <[EMAIL PROTECTED]> wrote:
Vemund Ostgaard <[EMAIL PROTECTED]> 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
