MySQL DB encoding problem

System information:

• 4.2.0-35-generic #40~14.04.1-Ubuntu
• DBeaver ver. 6.3.4.202002011957

Connection specification:

• MySQL ver. 5.7.19

Describe your question:

Hello,

I have several legacy MySQL databases which are created in latin1 charset but in fact data is stored in UTF8 encoding.

So I have to use “SET NAMES latin1” query each time I connect to these databases, no matter I do it manually or from scripts. After that query everything is alright with encoding.

But in DBeaver I cannot change the encoding using “SET NAMES latin1”.

(by the way, MySQL Workbench shows database contents in proper encoding after “SET NAMES latin1” query)

So the question is: may there be any kind of workaround for this situation?

mysql> select @@character_set_client, @@character_set_results, @@character_set_connection;                                                                                                                                                   +------------------------+-------------------------+----------------------------+
| @@character_set_client | @@character_set_results | @@character_set_connection |
+------------------------+-------------------------+----------------------------+
| utf8                   | utf8                    | utf8                       |
+------------------------+-------------------------+----------------------------+
1 row in set (0,00 sec)

mysql> select * from roles limit 3;
+--------+----------+----------------------------------------------------------+
| idrole | rolename | roletitle                                                |
+--------+----------+----------------------------------------------------------+
|      1 | admin    | ÐдминиÑтратор                               |
|      2 | guest    | ГоÑÑ‚ÑŒ                                               |
|      3 | default  | По умолчанию                                  |
+--------+----------+----------------------------------------------------------+
3 rows in set (0,00 sec)

mysql> SET NAMES latin1;
Query OK, 0 rows affected (0,00 sec)

mysql> select * from roles limit 3;
+--------+----------+----------------------------+
| idrole | rolename | roletitle                  |
+--------+----------+----------------------------+
|      1 | admin    | Администратор              |
|      2 | guest    | Гость                      |
|      3 | default  | По умолчанию               |
+--------+----------+----------------------------+
3 rows in set (0,00 sec)

mysql> SHOW CREATE TABLE roles;
| roles | CREATE TABLE `roles` (
  `idrole` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `rolename` varchar(45) NOT NULL,
  `roletitle` varchar(254) NOT NULL,
  PRIMARY KEY (`idrole`),
  UNIQUE KEY `rolename` (`rolename`)
) ENGINE=MyISAM AUTO_INCREMENT=22 DEFAULT CHARSET=utf8 |

[eloscuro]

[Feature request] Warning if “SET NAMES” command with MYSQL. Message will be with url https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-charsets.html Similar mechanism can be in PostgreSQL and Oracle DB.

Well, that might be a good idea, at least it will be less confusing, but it doesn’t solve the problem… 😦

[fkulakov]

Wow guys, I’m work the same job as you but I haven’t got those problem because I’m use DataGrip