Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
SQL garble?
I set up a test site with a new TXP 4.6.2 and compared the way non-ASCII characters would display and be stored in the database.
Here a
ÖÜÄ öüä
in backend/frontend finds itself changed in MySQL, to
ÖÜÄ öüä
That seems weird… (collation is utf8mb4)
I used to poke around in textpattern databases and even the weirdest UTF8 signs were appearing in body texts, scripts and what nots in clear text. That carried the advantadge of being able to edit straight in the database, if it didn’t work otherwise.
How could i turn my TXP 4.6.2 back to that kind of feature?
Last edited by jayrope (2016-11-29 15:21:14)
A hole turned upside down is a dome, when there’s also gravity.
Offline
Re: SQL garble?
Hi jayrope,
This post escaped me. To you check that the collation in the config.php file is also utf8mb4?
There is the htaccess rule which forces utf-8
AddDefaultCharset utf-8and I am wondering if you could change it to
AddDefaultCharset utf8mb4Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: SQL garble?
colak wrote #303480:
and I am wondering if you could change it to
AddDefaultCharset utf8mb4...
Don’t do that.
The “utf-8” that is specified in .htaccess covers both utf8 and utf8mb4. It’s only MySQL that treats them differently: utf8 is a subset of utf8mb4. The utf-8 in .htaccess is the same as utf8mb4.
Offline
Re: SQL garble?
ruud wrote #303482:
Don’t do that.
The “utf-8” that is specified in .htaccess covers both utf8 and utf8mb4. It’s only MySQL that treats them differently: utf8 is a subset of utf8mb4. The utf-8 in .htaccess is the same as utf8mb4.
Question> should one, when creating a new MySQL DB bother with specifying utf8mb4 … would simple utf8 be just as good?
…. texted postive
Offline
Re: SQL garble?
bici wrote #303485:
Question> should one, when creating a new MySQL DB bother with specifying utf8mb4 … would simple utf8 be just as good?
From the MySQL manual —
10.1.9.3 The utf8mb4 Character Set (4-Byte UTF-8 Unicode Encoding)
The character set named utf8 uses a maximum of three bytes per character and contains only BMP characters. As of MySQL 5.5.3, the utf8mb4 character set uses a maximum of four bytes per character supports supplementary characters:
- For a BMP character, utf8 and utf8mb4 have identical storage characteristics: same code values, same encoding, same length.
- For a supplementary character, utf8 cannot store the character at all, whereas utf8mb4 requires four bytes to store it. Because utf8 cannot store the character at all, you have no supplementary characters in utf8 columns and need not worry about converting characters or losing data when upgrading utf8 data from older versions of MySQL.
Offline
Re: SQL garble?
bici wrote #303485:
Question> should one, when creating a new MySQL DB bother with specifying utf8mb4 … would simple utf8 be just as good?
utf8mb4 supports more characters, like emoji.
Offline
Pages: 1