-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Surprising and inconsistent behavior depending on default locale #2672
Labels
Comments
One example:
This won't find the enum value with |
I see: https://stackoverflow.com/questions/30049590/string-format-prints-question-mark-as-output |
Also:
with And:
with |
ScottDugas
added
bug
Something isn't working
test failure
A test is failing at least some of the time
labels
Apr 22, 2024
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
Apr 24, 2024
…tting for locale If unspecified, collation `FunctionKeyExpression`s now set their locale to `Locale.ROOT` instead of the machine's default Locale. This makes the contents of index entries more resilient to users changing their machine's default values. This does mean that users who are running with an incompatible locale will need to update their index definitions to reference the appropriate locale or will need to rebuild any indexes that don't already set a locale. This fixes FoundationDB#2678. This is a specific instance of FoundationDB#2672.
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
May 8, 2024
…tting for locale If unspecified, collation `FunctionKeyExpression`s now set their locale to `Locale.ROOT` instead of the machine's default Locale. This makes the contents of index entries more resilient to users changing their machine's default values. This does mean that users who are running with an incompatible locale will need to update their index definitions to reference the appropriate locale or will need to rebuild any indexes that don't already set a locale. This fixes FoundationDB#2678. This is a specific instance of FoundationDB#2672.
alecgrieser
added a commit
to alecgrieser/fdb-record-layer
that referenced
this issue
May 8, 2024
…tting for locale If unspecified, collation `FunctionKeyExpression`s now set their locale to `Locale.ROOT` instead of the machine's default Locale. This makes the contents of index entries more resilient to users changing their machine's default values. This does mean that users who are running with an incompatible locale will need to update their index definitions to reference the appropriate locale or will need to rebuild any indexes that don't already set a locale. This fixes FoundationDB#2678. This is a specific instance of FoundationDB#2672.
MMcM
pushed a commit
that referenced
this issue
May 8, 2024
…cale (#2679) If unspecified, collation `FunctionKeyExpression`s now set their locale to `Locale.ROOT` instead of the machine's default Locale. This makes the contents of index entries more resilient to users changing their machine's default values. This does mean that users who are running with an incompatible locale will need to update their index definitions to reference the appropriate locale or will need to rebuild any indexes that don't already set a locale. This fixes #2678. This is a specific instance of #2672.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Some of the code in the record layer changes behavior based on the default locale of the system.
Most of this does not seem intentional.
The text was updated successfully, but these errors were encountered: