Feedback
Did this article resolve your question/issue?

   

Article

MySQL driver returns ParameterMetaData error from tables with apostrophe in the table name

Information

 
TitleMySQL driver returns ParameterMetaData error from tables with apostrophe in the table name
URL NameMySQL-driver-returns-ParameterMetaData-error-from-tables-with-apostrophe-in-the-table-name
Article Number000179174
EnvironmentProduct:Connect for JDBC MySQL driver
Version: 5.1.4.000154
OS: JAVA
Database: MySQL
Application: All supported applications
Question/Problem Description
MySQL driver returns ParameterMetaData error from tables with apostrophe in the table name when connecting with the Connect for JDBC MySQL driver.

For example, a table name like "MyTable'S" will cause the problem to occur.
Steps to Reproduce
Clarifying Information
Error MessageDataDirectOracle JDBC DriverThe requested parameter metadata is not available for the current statement.
Defect NumberDefect 61852
Enhancement Number
Cause
Mysql expects backtick(`)  as an identifierQuoteString to enclose tableName or column name. The driver was not handling the backtick correctly.
Resolution
Fixed in hot fix 5.1.4.000157

Refer to Connect for JDBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date1/4/2017 7:30 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.