Bug #28259 | Execute the MySQL Stored Procedure From ASP Page | ||
---|---|---|---|
Submitted: | 5 May 2007 10:18 | Modified: | 20 May 2007 22:02 |
Reporter: | Muthu K | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Connector / ODBC | Severity: | S1 (Critical) |
Version: | 5.0.37-community-nt-via TCP/IP | OS: | Windows (Win XP) |
Assigned to: | CPU Architecture: | Any |
[5 May 2007 10:18]
Muthu K
[5 May 2007 10:51]
Valeriy Kravchuk
Thank you for a problem report. What exact version of Connector/ODBC do you use? Note that as you were able to execute your procedure from the other environment, it is NOT a server's bug anyway. I am just not sure you can use user variables (like @Name) in VB code directly. You have to use prepared statement and bind parameters, among other things. Please, read the manual (http://dev.mysql.com/doc/refman/5.0/en/myodbc-examples-overview.html, http://dev.mysql.com/doc/refman/5.0/en/myodbc-usagenotes-apptips.html#myodbc-usagenotes-ap...) and links from it also.
[5 May 2007 11:17]
Muthu K
Hi My ODBC Version is below:- MyODBC-3.51.11-2-win.exe i changed the parameter name. (@DescID,@pName,@pConfig,@pBrand,@pInward,@bPrice,@pOutward,@sPrice)" ObjCmd.Parameters.Refresh objCmd.Execute , , adAsyncExecute it fired as below error:- Error Type: Microsoft OLE DB Provider for ODBC Drivers (0x80040E14) You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '{ call Stocks(@DescID,@pName, @pConfig,@pBrand,@pInward,@bPrice,@pOutward,@sPric' at line 1 /CRM/print/stock_report.asp, line 32 plz suggest me.
[5 May 2007 11:21]
Muthu K
hi plz mention syntax for execute the mysql stored procedure from asp page. thanks in advace.
[20 May 2007 21:47]
Tonci Grgin
Hi Muthu. I believe this is a duplicate of Bug#17898 but will look into it once again.
[20 May 2007 22:02]
Tonci Grgin
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Explanation: Muthu, see test cases and discussion in Bug#15635 please.