We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://media.dev.unee-t.com/2019-05-21/emoji-test.sh is a test that confirms this.
Perhaps encoding first/last name in base64 is a good workaround? https://dev.mysql.com/doc/refman/8.0/en/string-functions.html#function_to-base64 In the lambda I can base64 decode.
I've raised the issue with AWS https://console.aws.amazon.com/support/cases#/6092011631/en
The text was updated successfully, but these errors were encountered:
I asked AWS support about this in CASE 6092011631 and they replied:
In regards to your query "Can you confirm if this JSON_OBJECT bug has been fixed in aurora? https://stackoverflow.com/questions/45932774/mariadb-json-object-bad-encoding"
Yes this works well in Aurora Mysql and I have tested it, please note JSON is only supported in Aurora which is Mysql version 5.7 compatible.
Sorry, something went wrong.
Btw I've followed up again with my test case asking them to prove I'm not losing my mind.
Closing this duplicate to focus upon #73 (comment)
No branches or pull requests
https://media.dev.unee-t.com/2019-05-21/emoji-test.sh is a test that confirms this.
Perhaps encoding first/last name in base64 is a good workaround? https://dev.mysql.com/doc/refman/8.0/en/string-functions.html#function_to-base64
In the lambda I can base64 decode.
I've raised the issue with AWS https://console.aws.amazon.com/support/cases#/6092011631/en
The text was updated successfully, but these errors were encountered: