[
https://issues.apache.org/jira/browse/DERBY-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112948#comment-13112948
]
Dag H. Wanvik commented on DERBY-5420:
--------------------------------------
A solution may be to save the default locale at the time of creating the
decimal format, and check if the default locale has changed before deciding to
use the hashed value or recompute it. The current code is an optimization,
hopefully retrieving the current default locale will not void the optimization
entirely.
> TableLockBasicTest is locale sensitive: failed with Norwegian locale on
> Windows.
> --------------------------------------------------------------------------------
>
> Key: DERBY-5420
> URL: https://issues.apache.org/jira/browse/DERBY-5420
> Project: Derby
> Issue Type: Bug
> Components: Test
> Environment: Windows Vista SP2, Norwegian locale, JDK 7.
> Reporter: Dag H. Wanvik
> Priority: Minor
>
> The execution plans are asserted in this test and I saw this diff:
> Expected:
> :
> optimizer estimated row count: 6.00
> optimizer estimated cost: 100.40<
> Found:
> :
> optimizer estimated row count: 6,00
> optimizer estimated cost: 100,40<
> the latter using a decimal comma whereas a decimal point is expected.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
