Bug #9319 | same name procedure in diferent databases | ||
---|---|---|---|
Submitted: | 21 Mar 2005 19:06 | Modified: | 31 May 2005 15:50 |
Reporter: | Sergi Vergés | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: User-defined functions ( UDF ) | Severity: | S2 (Serious) |
Version: | 5.0.3-beta-nt | OS: | Windows (Windows XP sp2) |
Assigned to: | CPU Architecture: | Any |
[21 Mar 2005 19:06]
Sergi Vergés
[24 Mar 2005 18:31]
Mark Matthews
Does this error happen if you fully qualify the stored procedure name? (i.e. code like this): cstmt = ( CallableStatement )conn.prepareCall( "{ call db1.COMPROVAR_USUARI(?, ?, ?, ?, ?, ?) }" ); or alternatively: cstmt = ( CallableStatement )conn.prepareCall( "{ call " + conn.getCatalog() + ".COMPROVAR_USUARI(?, ?, ?, ?, ?, ?) }" );
[29 Mar 2005 11:05]
Sergi Vergés
Yes and no, using this two options you specified I get an error but not the same error. java.sql.SQLException: Parameter index of 2 is out of range (1, 0) at com.mysql.jdbc.CallableStatement.checkParameterIndexBounds(CallableStatement.java:1002) at com.mysql.jdbc.CallableStatement.checkIsOutputParam(CallableStatement.java:971) at com.mysql.jdbc.CallableStatement.registerOutParameter(CallableStatement.java:864).....
[11 Apr 2005 10:30]
Sergi Vergés
I've tried the 5.0.3 beta server version and I've reproduced the error.
[11 May 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[31 May 2005 15:37]
Jorge del Conde
Thanks for your bug report. I was able to reproduce this bug using 5.0.3
[31 May 2005 15:50]
Mark Matthews
This is fixed in the nightly snapshots of 3.1.x, see http://downloads.mysql.com/snapshots.php