MySQL Bugs: #48720: using mysql stored procedures from client systems is screwed

Bug #48720	using mysql stored procedures from client systems is screwed
Submitted:	12 Nov 2009 8:11	Modified:	30 Aug 2010 7:46
Reporter:	Paul nisbett	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / J	Severity:	S3 (Non-critical)
Version:	5.1	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
using stored procedures from client applications like Java is completely fucked .

Apparently everybody that tries  it gets this rather useless message:
User does not have access to metadata required to determine stored procedure parameter types. If rights can not be granted, configure connection with "noAccessToProcedureBodies=true" to have driver generate parameters that represent INOUT strings irregardless of actual parameter types.

How to repeat:
Try calling a stored procedure with parameters from java as per your shitty ass documentation.

Suggested fix:
Fix your documentation !

After googling this problem that a lot of people are having , the posted fix
of adding &noAccessToProcedureBodies=true" to the connection string
 does not work .

Hi Paul and thanks for your report.

From your report, I am not sure what the actual problem is.
Is it just documentation? If so, please paste the link to offending page with your explanation.
If it's code, please attach small but complete test case demonstrating unwanted behavior. You will find many good bug reports in bugsdb and in c/J sources, maybe Bug#28689 will provide you with enough info to make usable one.

Please do note MySQL server, JDK and c/J version used.

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".