-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: error caused by collated string comparison #56335
Labels
A-sql-typing
SQLtype inference, typing rules, type compatibility.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Comments
rafiss
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
A-sql-typing
SQLtype inference, typing rules, type compatibility.
labels
Nov 5, 2020
rafiss
changed the title
sql: error in v20.1 caused by collated string comparison
sql: error caused by collated string comparison
Nov 5, 2020
Actually this also fails in logic tests on 20.2, with the |
This was referenced Nov 16, 2020
It looks like this is bug still exists. The logic tests below cause the same internal error. However, the I can't get the same SQL to produce an error in
If cc @rafiss |
craig bot
pushed a commit
that referenced
this issue
Mar 25, 2021
62562: sql: fix internal error when comparing collation names r=otan,mgartner a=rafiss fixes #56335 (that issue was previously closed and just got reopened) Release note (bug fix): An internal error caused by comparing collation names that had different upper/lower case is now fixed. Co-authored-by: Rafi Shamim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-sql-typing
SQLtype inference, typing rules, type compatibility.
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
Describe the problem
A normal SELECT query over collated strings can cause an error. A customer bug report also claims there was a panic and node crash.
Even if only
collatedstring{en-US-u-ks-level2}
is used, the error message says that the query doesn't work because it thinkscollatedstring{en-us-u-ks-level2}
is being used.To Reproduce
Environment:
v20.1
Additional context
The error seems fixed in v20.2.0-alpha.2
The text was updated successfully, but these errors were encountered: