-
Notifications
You must be signed in to change notification settings - Fork 976
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
Lost Connection after calling Stored Procedure for ProxySQL v2.0.4 #2059
Comments
Bug verified, and a patch is ready. PR #2060 |
Fixed in 2.0.5 . |
We confirm you the bug is solved for console app in 2.0.5. But if you try to do the same by using C-API or other connectors like Ruby/mysql2, zdb..., any client queries with stored procedure go to halting. In case of C-API, when mysql_stmt_next_result method is called the system freezes. |
Re-opening until verified/fixed. |
@renecannao
|
@renecannao: the same code written in ruby. `#!/usr/bin/env ruby raise "#{FILE} " if ARGV.size < 5 dbhost = ARGV[ 0 ] begin
rescue Exception => e |
my previous the statement:
is not correct. You have to use stored procedure and prepare statement together if you want to reproduce the malfunction. The following C-code without prepare statement works.
|
@qed-motore : thanks for the sample code. |
@renecannao Any updates on this issue? Due to this we are not able to take proxysql to our production!! |
I'm facing this issue too. Calling storedproc to proxysql via PHP failed for me as well. |
Dealing with the same issue here as well. Whenever the client issues a CALL() query, it gets no answer from ProxySQL. |
This problem seems not to be solved. I'm currently dealing with it in a golang app. Any update? |
@renecannao do we know how this can be solved, this seems like an important ask. While exploring proxy-sql, it fits almost all of our use cases except for this one for now. |
The text was updated successfully, but these errors were encountered: