Stored Proc name conflict
Posted: Sun 27 Oct 2013 08:17
Hi,
I have been using dbExpress with pleasure for a year now. However, there is one problem that bothers me. I have a MySQL database with two different schema, say "db_prod" and "db_test". One is the test database, the other one for production. However, if both schema contain a stored procedure that has the same name, then there seems to be some kind of conflict and dbExpress gets mixed up in the number of parameters.
I give an example of such a simple stored procedure. It is important that both schema contain the same procedure with the same name :
And I create a TSQLStoredProc object in my code :
The last line fires an exception at runtime :
Thanks in advance,
I have been using dbExpress with pleasure for a year now. However, there is one problem that bothers me. I have a MySQL database with two different schema, say "db_prod" and "db_test". One is the test database, the other one for production. However, if both schema contain a stored procedure that has the same name, then there seems to be some kind of conflict and dbExpress gets mixed up in the number of parameters.
I give an example of such a simple stored procedure. It is important that both schema contain the same procedure with the same name :
Code: Select all
CREATE PROCEDURE `GetNumber`(OUT `myNumber` INT)
BEGIN
SET myNumber = 3;
ENDCode: Select all
// myConnection is a TSQLConnection object connected to 'db_test'
TSQLStoredProc* sp = new TSQLStoredProc(myConnection);
sp->SQLConnection = myConnection;
sp->StoredProcName = "GetNumber";
sp->ExecProc();Has anyone seen this before ? Or is this a MySQL bug ?TDBXError : Incorrect number of arguments for PROCEDURE GetNumber ; expected 1 got 2;
Thanks in advance,