MySQL Bugs: #44599: User variables interpreted as Parameters

Bug #44599	User variables interpreted as Parameters
Submitted:	1 May 2009 11:38	Modified:	1 May 2009 16:12
Reporter:	Guy Moreau	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	6.03	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	crash, regression

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
When an SQL statement with user variables are attempted to be executed, .NET connector returns with 'Parameter @ is not defined'. These SQL statements have been developed and tested using MySQL Query Browser and work no problem there.

This used to work in a previous version of the Connector, not sure which.

How to repeat:
run this from .net and it fails with parameter not defined:
set @a = 'select * from clients';

prepare atexe from @a;
execute atexe;

Suggested fix:
Provide a method to identify user variables (MarkupVariable(string VarName)??) or auto detect user variables.

Please set the 'allow user variables=true' connection string option to support this case