Tagged articles
utf8
11 articles · Page 1 of 1
This article explains why MySQL's utf8 character set only supports up to three bytes per character, causing failures with emoji and complex characters, and details the historical reasons behind this limitation, recommending utf8mb4 for full UTF-8 support.
MySQLRFC 3629UTF-8
0 likes · 10 min read

MySQL's utf8 character set only supports up to three bytes per character, causing errors when storing emoji or complex characters that require four bytes; the article explains the historical reason for this limitation and demonstrates that utf8mb4 is the true UTF-8 implementation introduced in 2010.
MariaDBMySQLUTF-8
0 likes · 9 min read

This article walks through eight often‑overlooked Go features—including direct integer iteration in Go 1.22, the ~T generic constraint, UTF‑8 string length pitfalls, nil‑interface quirks, nil‑pointer method calls, proper timer usage with contexts, zero‑size struct semaphores, and the JSON "-" tag—showing concrete code examples and the reasoning behind each behavior.
ContextGenericsGo
0 likes · 9 min read

MySQL’s original utf8 implementation was a limited, buggy version that only supported three‑byte characters, leading to data loss for emojis and rare symbols, so MySQL introduced utf8mb4 as a full UTF‑8 solution and now recommends it as the default encoding.
MySQLcharacter-setdatabases
0 likes · 5 min read


ITPUBNov 3, 2025 · Databases
Although MySQL historically labeled its three‑byte character set as “utf8”, it actually implements a truncated version (utf8mb3) that cannot store the full Unicode range, leading to bugs with emojis and rare characters; the newer utf8mb4 restores true UTF‑8 support and is now the default in MySQL 8.0.
MySQLUnicodecharacter-set
0 likes · 7 min read

A collection of Zhihu answers explains that MySQL’s original utf8 charset only supports three‑byte characters, causing data loss for emojis and rare symbols, and shows how the newer utf8mb4 charset provides full Unicode support, becoming the default in MySQL 8.0.
MySQLcharacter-setutf8
0 likes · 7 min read

Discover why MySQL’s legacy ‘utf8’ charset only supports three‑byte characters, causing storage errors for true UTF‑8 data, and learn how the ‘utf8mb4’ charset resolves these issues, with historical context, technical details, and migration guidance.
MariaDBMySQLcharacter-set
0 likes · 7 min read

This article explains MySQL's various character sets and collations, describes important system variables such as character_set_client and character_set_connection, demonstrates how to query supported encodings, and provides practical examples for avoiding and fixing garbled text caused by mismatched encodings.
MySQLUTF32encoding
0 likes · 10 min read

A colleague encountered an "Incorrect string value" error when inserting UTF‑8 text into a GBK‑encoded MySQL table, and the article explains how charset mismatches and the use of the CHAR() function cause the failure, then provides reproducible tests and concrete solutions.
CharsetGBKINSERT error
0 likes · 6 min read

The article explains that MySQL’s legacy "utf8" charset only supports three‑byte sequences, causing errors with true four‑byte Unicode characters, and shows how the later "utf8mb4" charset provides proper UTF‑8 support along with historical context and migration guidance.
MariaDBMySQLcharacter-set
0 likes · 8 min read


ITPUBOct 18, 2016 · Databases
This guide explains the three essential character sets—operating system (LANG), Oracle database (NLS_CHARACTERSET), and client (NLS_LANG)—and provides step‑by‑step instructions with screenshots to resolve SQL*Plus display garbling issues.
NLS_LANGOracleSQLPlus
0 likes · 6 min read
