-
Notifications
You must be signed in to change notification settings - Fork 2
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
Custom upper() function gives wrong results #34
Comments
Hi @DanielSWolf I just found this ticket. My apologies for the delay. I may need some time to double-check my understanding of this issue before working on a solution. As you may know, the code would need to be updated in this project: https://github.com/brodybits/sqlite3-eu This means that I may be able to get this fixed in this repo ... which could expedite the validation from your side. |
Hi @brodybits, No problem about the delay. Thanks for looking into it! |
The fix should be as easy as changing the three incorrect Unicode code points in your lookup table. I've just created a PR: brody4hire/sqlite3-eu#1 |
Thanks @DanielSWolf for contributing the quick solution ... just merged! I am now reopening this issue with some TODO items:
|
This repo contains a custom
upper()
function, implemented in #21. We just discovered that there are three characters that aren't handled correctly in this function. It seems that this is my fault, as these errors are contained in the original character table I gave you in #21.@brodybits This bug isn't critical by any means. Maybe it could be fixed in the course of porting our custom features to the official repo.
*Note: "Latin Capital Letter D with Stroke" and "Latin Capital Letter Eth" are visually identical, but have different Unicode code points.
We're tracking this issue internally as PRDXMIP-2391.
The text was updated successfully, but these errors were encountered: