Bug #87011 Connector/Net cannot debug a stored procedure calling SP has a name 2dt2.
Submitted: 11 Jul 2017 13:21 Modified: 11 Jul 2017 13:45
Reporter: Meiji Kimura Email Updates:
Status: Verified Impact on me:
None 
Category:Connector / NET Severity:S3 (Non-critical)
Version: OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[11 Jul 2017 13:21] Meiji Kimura
Description:
Similar to Bug #86978.

Based on historical reason, MySQL can deal with a SP(Stored Procedure) name start with numerical character without `

CREATE PROCEDURE 2dt2()

But if a stored procedure call the SP has a name like this, Connector/Net cannot debug the stored procedue with this error message.

line3:1 no viable alternative at input 'call'. Expected proc_name.

How to repeat:
Add these stored procedures, and try to debug them with this procedure.

https://dev.mysql.com/doc/visual-studio/en/visual-studio-debugger.html

only c2dt2 shows no viable alternative errors.

-- OK
drop procedure if exists 2dt2;
delimiter $$
CREATE PROCEDURE 2dt2()
begin
DROP TABLE IF EXISTS aa;
CREATE TABLE aa(i1 int);
end$$
delimiter ;

-- NG line3:1 no viable alternative at input 'call'. Expected proc_name.
drop procedure if exists c2dt2;
delimiter $$
CREATE PROCEDURE c2dt2()
begin
call 2dt2();
end$$
delimiter ;

-- OK
drop procedure if exists c2dt2i;
delimiter $$
CREATE PROCEDURE c2dt2i()
begin
call `2dt2`();
end$$
delimiter ;

Suggested fix:
Should be able debug c2dt2,

or 

Add limitation statement to this manual.
https://dev.mysql.com/doc/visual-studio/en/visual-studio-debugger.html
[11 Jul 2017 13:45] Chiranjeevi Battula
Hello Meiji,

Thank you for the bug report and test case.
Verified this behavior on Visual Studio 2013 (C#.Net) and Connector/NET 6.9.9 version.

Thanks,
Chiranjeevi.
[11 Jul 2017 13:45] Chiranjeevi Battula
Screenshot

Attachment: 87011.JPG (image/jpeg, text), 110.04 KiB.