Bug #26071 | getParameterMetaData error when return resultSet is specified | ||
---|---|---|---|
Submitted: | 5 Feb 2007 6:39 | Modified: | 6 Mar 2007 17:39 |
Reporter: | Sue-Yen Tsai | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 5.04 | OS: | Windows (Windows 2000) |
Assigned to: | CPU Architecture: | Any |
[5 Feb 2007 6:39]
Sue-Yen Tsai
[5 Feb 2007 10:23]
Tonci Grgin
Hi Sue-Yen Tsai and thanks for your report. I would like to see JRE, OS and MySQL server details as well as complete test case attached to this report before proceeding.
[5 Feb 2007 10:28]
Tonci Grgin
Hi. This may be connected to Bug#17898, "No straightforward way to deal with output parameters". Waiting on your test case.
[5 Feb 2007 14:04]
Mark Matthews
You've used the syntax for calling a stored _function_ ({?=call(?...)}. Therefore the bug isn't that parameter metadata has an error, you _should_ be getting an error message that there isn't a function that has the required parameters or name. The leading ?= doesn't mean that the procedure being called has a result set, it means it has a return _value_ (i.e. a function). You don't have to declare anything with MySQL for callable statements that return result sets, you just retrieve them.
[5 Feb 2007 18:15]
Sue-Yen Tsai
Thanks for reply. I am using JDK 1.6 and the MySQL is 5.0.27-community-nt
[5 Feb 2007 18:17]
Sue-Yen Tsai
Thanks Mark. I will try the solution you posted
[5 Feb 2007 18:35]
Sue-Yen Tsai
Thanks for the help. Sorry for the confusion. It worked as Mark posted. I removed the ?= before the CALL and retrieve the result set without problem
[6 Mar 2007 17:39]
Tonci Grgin
I'm closing this report as there seems to be no actual problem.