Bug #21292 | Cannot call stored procedure with JDBC without select_priv on mysql.proc | ||
---|---|---|---|
Submitted: | 26 Jul 2006 8:52 | Modified: | 1 Aug 2006 0:31 |
Reporter: | Kristian Koehntopp | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | Connector/J 3.1.12 | OS: | Linux (SLES 9) |
Assigned to: | CPU Architecture: | Any | |
Tags: | jdbc, privileges, stored procedure |
[26 Jul 2006 8:52]
Kristian Koehntopp
[26 Jul 2006 8:58]
Tonci Grgin
Seems non OS, non JDBC version dependent since it's repeatable on, for example, XP with 3.1.12, 3.1.13 and 5.0 2006-07-04 snapshot. Checking more.
[31 Jul 2006 23:00]
MySQL Verification Team
Please see bug: http://bugs.mysql.com/bug.php?id=20235 too.
[1 Aug 2006 0:31]
Mark Matthews
As already discussed w/ reporter of bug, this is not a bug, but a limitation of the server, as the JDBC specification _requires_ metadata from stored procedures about _parameters_ (i.e result sets don't help here!) that is currently only available in the body of the stored procedure, since we haven't yet implemented INFORMATION_SCHEMA.parameters in the server. Other drivers (ODBC, ADO.Net) that support actual types for parameters beyond string/number a'la PHP/Perl require the same information and use similar mechanisms to retrieve it. See "noAccessToProcedureBodies" in /J 5.0.3 for a somewhat hackish, non-JDBC compliant workaround.