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

SET GLOBAL support #6647

Closed
mcronce opened this issue Aug 28, 2020 · 1 comment · Fixed by #6957
Closed

SET GLOBAL support #6647

mcronce opened this issue Aug 28, 2020 · 1 comment · Fixed by #6957

Comments

@mcronce
Copy link

mcronce commented Aug 28, 2020

Feature Description

While SET works, SET GLOBAL does not. In particular, what I've found not working is SET GLOBAL sql_mode = 'TRADITIONAL', but from what I've been able to tell we haven't added support for SET GLOBAL in general

Use Case(s)

I found this while doing testing for various frameworks. In particular, the Rust mysql and mysql_async crates use it. However, from what I can tell, they only use it for integration tests (cargo test) - actually writing an application using the framework works perfectly fine. If anybody else comes across a more urgent use case, this would be a great place to record it :)

@systay
Copy link
Collaborator

systay commented Aug 29, 2020

We can't really do this at this moment. Not sure what a good way of handling it would be. Should we just ignore these SET queries, or just apply the settings in the session scope? Or is this one of those cases where the user has to configure MySQL with these settings, and then we could just let them be NoOps. WDYT? /cc @sougou @harshit-gangal

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 a pull request may close this issue.

2 participants