Bug #7133 Invalid query string when using inout parameters
Submitted: 9 Dec 2004 16:15 Modified: 9 Dec 2004 20:46
Reporter: Paul Hyman Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S2 (Serious)
Version:1.0.2 OS:Windows (Windows2000)
Assigned to: Reggie Burnett CPU Architecture:Any

[9 Dec 2004 16:15] Paul Hyman
When calling a stored procedure with inout parameters, connector/net constructs a query consisting of a SET statement followed by the call.  However, an extra semicolon is placed in the string, which looks something like:
SET ?12345parameter=value;;call procedure(...);

This is happening because when the SET string is being built, after each parameter is added to the set statement a semicolon is placed at the end of the string and when the entire SET string has been constructed another semicolon is added.  This last semicolon is not needed and causes the query to fail.

How to repeat:
Create a stored procedure with an inout parameter and call it from .NET code.

Suggested fix:
remove the statement adding the final semicolon.
[9 Dec 2004 20:46] Reggie Burnett
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at