CONJ-665.patch
|
Problem/Incident |
|||
| is caused by |
|
default collation use utf8mb4 if serv... | Closed |
[CONJ-665] Old MySQL doesn't support utf8mb4 Created: 2018-12-07 Updated: 2019-02-08 Resolved: 2018-12-18 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | MySQL compatibility |
| Affects Version/s: | 2.3.0 |
| Fix Version/s: | 1.8.0, 2.4.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Erik Karlsson | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Linux, Brighthouse with MySQL 5.1.40 |
||
| Attachments: |
CONJ-665.patch
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
MySQL 5.5.3 introduced the charset utf8mb4, but I'm trying to use the connector with version 5.1.40, which does not support this. Unfortunately, since the server doesn't support the encoding, it falls back to its default, which is latin1 and since the connector doesn't use the charset returned in the resultsets, the strings created contains character encoding errors. Since the server greeting contains the version, is it possible to fall back to utf8 (utf8mb3) on older releases? |
| Comments |
| Comment by Diego Dupin [ 2018-12-18 ] |
|
MySQL 5.1 is not supported anymore, but since correction is easy (and done) |