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
"#2014 - Commands out of sync; you can't run this command now" returned when stored procedure does not return any result set #14614
Comments
|
Stackoverflow: https://stackoverflow.com/a/20435243/5155484 |
|
@javide I remember having this issue, can you please explain how to reproduce this issue ? |
|
Create the procedure DELIMITER $$
CREATE PROCEDURE `abc`()
NO SQL
(SELECT * FROM mysql.user WHERE 0)
UNION
(SELECT * FROM mysql.user WHERE 0)$$
DELIMITER ;And run CALL abc() |
…his command now" returned when stored procedure does not return any result set Fixes: phpmyadmin#14614 Signed-off-by: William Desportes <williamdes@wdes.fr>
…log'] = true; Fixes: phpmyadmin#14614 Signed-off-by: William Desportes <williamdes@wdes.fr>
|
Found the solution on https://community-auth.com/blog-posts/commands-out-of-sync-error-when-using-stored-procedures Fixed by 9178602 |
…log'] = true; Fixes: phpmyadmin#14614 Signed-off-by: William Desportes <williamdes@wdes.fr>
Signed-off-by: William Desportes <williamdes@wdes.fr>
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Describe the bug
In phpMyAdmin 4.8.3 if you call a stored procedure that contains a SELECT statement, when this SELECT does not return a result set, this error is displayed:
#2014 - Commands out of sync; you can't run this command nowWhen calling the same stored procedure from the mysql command line the expected output is returned instead:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Server configuration
Client configuration
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: