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.

Sign up for GitHub

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

Jump to bottom

Add support for SET CHARACTER SET #1692

Closed
renecannao opened this issue Sep 15, 2018 · 3 comments
Closed

Add support for SET CHARACTER SET #1692

renecannao opened this issue Sep 15, 2018 · 3 comments
Assignees
@renecannao
Labels
CONNECTION POOL PROTOCOL
Milestone
v2.0.0

Comments

@renecannao
Copy link
Contributor

ProxySQL properly supports SET NAMES , but not SET CHARACTER SET neither SET CHARSET.

This is a follow up from #780 (comment)
@renecannao renecannao added this to the v2.0.0 milestone Sep 15, 2018
@renecannao renecannao self-assigned this Sep 15, 2018
@renecannao renecannao mentioned this issue Sep 15, 2018
Open
renecannao added a commit that referenced this issue Sep 21, 2018
@renecannao
Support for SET CHARACTER and SET CHARSET #1692
f6fea64 
This implementation is specific to 1.4.x
@renecannao
Copy link
Contributor Author

Support implemented in 1.4.12 .
in 2.0.0 this will implemented in a different way.

@terrywh
Copy link

terrywh commented Apr 14, 2019

any news on this ?

@Dieken
Copy link
Contributor

Dieken commented May 7, 2019

The fix was committed to 1.4.12, not >= 1.4.13.

@alpes214 alpes214 mentioned this issue Oct 15, 2019
Closed
renecannao added a commit that referenced this issue Oct 21, 2019
@renecannao
Fixing logic for SET CHARACTER SET #1692
630e66f
alpes214 pushed a commit to alpes214/proxysql that referenced this issue Oct 21, 2019
@renecannao
Fixing logic for SET CHARACTER SET sysown#1692
13db58b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@renecannao renecannao

Labels
CONNECTION POOL PROTOCOL
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
3 participants
@Dieken @terrywh @renecannao