Feedback
Did this article resolve your question/issue?

   

Article

Can’t query BIT datatype using a stored procedure with the MySQL driver

Information

 
TitleCan’t query BIT datatype using a stored procedure with the MySQL driver
URL NameCan-t-query-BIT-datatype-using-a-stored-procedure-with-the-MySQL-driver
Article Number000183023
EnvironmentProduct: Connect for ODBC MySQL driver
Version: 7.16.0173
OS: All supported platforms
Database: MySQL
Application: All supported applications
Question/Problem Description
Can’t query BIT datatype using a stored procedure with the Connect for ODBC MySQL driver
Steps to Reproduce
Clarifying Information
When using a stored procedure to query data containing the BIT data type, the driver returned an “Invalid character value” error.
Error MessageDataDirectODBC MySQL Wire Protocol driver Invalid character value. Error in column x
Defect Number41101
Enhancement Number
Cause
The conversion from INTERNAL_TYPE_CODEPAGE to CType(SQL_C_TINYINT) failed because it is an invalid conversion.
Resolution
Fixed in hot fix 07.16.0175

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 Date7/6/2016 7:54 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.