-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
JSON string comparison seems broken (change in behavior from v0.6.0 and v0.10.0) #474
Comments
Would you like a PR that fixes this behavior? |
We would love one.
…On Mon, Jun 21, 2021 at 11:50 AM andremarianiello ***@***.***> wrote:
Would you like a PR that fixes this behavior?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#474 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJAR3B77NFMJGUZANERBCDTT6CW3ANCNFSM464CITIA>
.
|
Looks like @bheni made a change it HEAD that fixes the unquoted behavior, but the quoted behavior still doesn't match with MySQL. With 8571009
I'll make a PR to fix the quoted behavior. |
Nevermind, looks like I was beaten to the punch. Thanks @ajnavarro ! |
Woops! Sorry @andremarianiello ! We were on sync ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a MySQL server
With go-mysql-server v0.6.0
With go-mysql-server v0.10.0
The comparison is now false and unquoting fails completely. I believe the root cause is sql.LongText.Convert failing to handle JSONDocument values, so Equals.Compare ends up converting the json value to nil.
The text was updated successfully, but these errors were encountered: