Why does TeamSpeak/MySQL save Unicode characters as ASCII?

[PatPeter]

I converted my TeamSpeak 3 server from SQLite to MySQL and I've noticed some very strange behavior in regards to TeamSpeak saving Unicode characters. For instance, someone joined my server with the following name:

あっちゃんさん

But in the clients table, it is saved as:

���ゃん�ん

I've tried every Unicode collation on MySQL, but to no avail. It saves this way no matter what. Is this a bug or does TeamSpeak have to save this way for compatibility with SQLite?

[PatPeter]

Can anyone else confirm that this happens to him or her?

[PatPeter]

Anyone want to look into their MySQL database?

[PatPeter]

According to SELECT * FROM information_schema.SCHEMATA; my database is utf8 / utf8_general_ci for its character set / collation. All of the tables in my database match as well. However, UTF8 characters are still being saved as single-byte characters.

[ANR Daemon]

Let me guess.
You used MySQL "root" or equivalent user with SUPER privilege to connect to the database?

[PatPeter]

Does anyone know which script it was that fixed this issue in a prior version of TeamSpeak 3? I need to re-run it for an old backup of my database.

Let me guess.
You used MySQL "root" or equivalent user with SUPER privilege to connect to the database?

Why would that have anything to do with bad encoding of text fields in the database?

[ANR Daemon]

Because a user with SUPER privileges ignores incorrectly set connection charset (and some other minor errors, which for a regular user would cause connection failure).

Oh, also,
http://mysqlserverteam.com/sushi-bee...-in-mysql-8-0/
http://mysqlserverteam.com/new-colla...n-mysql-8-0-0/
http://mysqlserverteam.com/mysql-8-0...n-the-details/

[numma_cway]

Why are people moving from SQLite to something with generally less performance?

[ANR Daemon]

Out of ignorance, mostly.