-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Prepared statement queries returning NULL results not being parsed #6240
Milestone
Comments
aquarapid
added a commit
to planetscale/vitess
that referenced
this issue
May 31, 2020
…gth offset into account in writeBinaryRow(). Not an ideal fix, but something cleaner will involve invasive cleanup. Signed-off-by: Jacques Grove <aquarapid@gmail.com>
aquarapid
added a commit
that referenced
this issue
Jun 1, 2020
aquarapid
changed the title
Queries returning NULL results not being parsed
Prepared statement queries returning NULL results not being parsed
Jun 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview of the Issue
Using
the latest releasemaster the OK packet is missing extra data. Any release fromv6.0.20-YYYYMMDD
is working as expected.Reproduction Steps
Steps to reproduce this issue, example:
vschema
:schema
:INSERT INTO user (username, age) VALUES ("u1", 18)
SELECT AVG(age) FROM user WHERE username = 'user1'
orSELECT fake FROM user WHERE username = 'u1'
The command was run with
MyXQL
library for Elixir which returns:Checking the exchanged packets all are the same expect the OK packet which is missing the extra data when responding to the execute statement.
Binary version
Operating system and Environment details
Using vitess operator with Kubernetes version 1.15
MariaDB 10.3.22
Running with:
Log Fragments
The logs do not show any issue.
The text was updated successfully, but these errors were encountered: