From Oracle:
What do you need to know about free software?
Users who install Connector/ODBC and register it to the ODBC manager manually can choose to install and register either one or both of the drivers; the different drivers are identified by a w (for “ wide characters ”) for the Unicode driver and a for the ANSI driver at the end of the library names. Direct, real-time access to MySQL, no import/export necessary, ensuring your analysis is based on the most recent data. Read-write driver, maximising the integration potential for MySQL and client applications.
I have been stuck up in this scenario.
My application is in C++ which connects to MySQL database 5.5.34 through MySQL odbc connector v5.2 Unicode Driver.
My tables were using the character set and collation properties 'utf-8'. To insert supplementary unicode characters, i changed it via
My table was initially created:
After this, I am able to directly (not through my app) insert the supplementary characters into the column holding 'TEXT' data type.
The odbc connector crashes when it encounters supplementary characters.
The following are some of my my.ini configurations.
The query that i am trying to insert:
any pointers/heads up would be great.
Also, tried using v5.3 Unicode MYSQL odbc connector and v1.0.5 MariaDB ODBC connector, still the same.
Thanks in advance.
2 Answers
The workaround here is to use MariaDB odbc connector to connect to MySQL database.https://mariadb.com/my_portal/download/connector-odbc/1.0
Make sure you set this in ODBC dsn and keep Connection Character Set empty
Download Mysql Odbc Drivers
Starting v5.2 of MyODBC, SET NAMES has been deprecated. Hence the need to use MariaDB connector. Hope the supplementary character issue is fixed in MySQL odbc connector.
You need to issue SET NAMES utf8mb4 after connecting to MySQL. Otherwise, the connection cannot handle the 4-byte characters.
Mysql Odbc Install
If that is not sufficient, then chase down SQLExecDirectW -- see if there is an update to it.