Skip to content
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

Fix(mysql): Invaild column definitions lead to incorrect mariadb-client behavior #13

Merged
merged 1 commit into from
Mar 30, 2022

Conversation

junnplus
Copy link
Contributor

Signed-off-by: Ye Sijun junnplus@gmail.com

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

databendlabs/databend#4429

@junnplus
Copy link
Contributor Author

/review @sundy-li @PsiACE

mysql/src/lib.rs Outdated Show resolved Hide resolved
Signed-off-by: Ye Sijun <junnplus@gmail.com>
// and will be removed in a future version.
// The mysql command line tool issues one of these commands after switching databases with USE <DB>.
// Return a invalid column definitions lead to incorrect mariadb-client behaviour,
// see https://github.com/datafuselabs/databend/issues/4439
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But will this make incorrect to old mysql client behavior?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not returning column definitions is acceptable behavior for the client. column information is used as completion, no return is better than invalid.

I also tested mysql-client 5.7 locally, it works.

@sundy-li sundy-li merged commit 22c7f23 into databendlabs:main Mar 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants