[
https://issues.apache.org/jira/browse/DERBY-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113153#comment-13113153
]
Bryan Pendleton commented on DERBY-5420:
----------------------------------------
Great catch! And thanks for the clear description of the behavior; it makes
complete sense.
It's always nice to find a deterministic answer :)
My initial reaction to the code you pasted in your earlier comment is that it
seems like
the sort of thing that should be done in the ResultSetStatistics constructor.
That is, it seems like the "df" object should not be static, and the code to
set it up based
on the current locale should be in the constructor.
I'm not sure if that would be a performance problem, but it might be a place to
start.
> 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
