Tagged articles
utf8mb4
43 articles · Page 1 of 1
This tutorial demonstrates MySQL 8.0 configuration of character sets, collations, time zones, and SQL modes through reproducible experiments, showing how connection settings differ from server defaults, how utf8mb4 handles emojis, why TIMESTAMP converts across time zones while DATETIME does not, and how strict SQL mode rejects out-of-range values.
MySQLcharacter-setcollation
0 likes · 20 min read

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

The article explains the difference between character sets and encodings, shows that MySQL’s utf8 is actually an alias for utf8mb3, demonstrates how using the wrong charset or collation causes garbled data, and provides practical steps to consistently use utf8mb4 across versions and connections.
MySQLcharacter-setcollation
0 likes · 13 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

This article explains MySQL's supported character sets and collations, shows how to list them, demonstrates table‑level and column‑level definitions, clarifies naming conventions, and provides practical examples for verifying and altering collations to ensure correct string comparison and storage.
MySQLSQLcharacter-set
0 likes · 10 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

Learn how to diagnose and permanently fix MySQL character set problems—like garbled Chinese text or missing emoji—by checking current settings, altering databases and tables to utf8mb4, updating the my.cnf configuration, and avoiding common pitfalls, all with clear command examples.
MySQLSQLcharacter-set
0 likes · 5 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

This article explains why inserting emoji characters into a MySQL table defined with the default utf8 charset triggers a string‑value error, explores the underlying encoding and charset concepts, compares utf8mb3 and utf8mb4, and shows how to convert tables to avoid such failures.
MySQLcharacter-setcollation
0 likes · 9 min read

This article explains why MySQL’s built‑in utf8 charset only supports three‑byte characters, why emojis cause errors, and how switching to the proper utf8mb4 charset resolves insertion issues while preserving full Unicode support.
MySQLcharacter-setdatabase
0 likes · 9 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

The article explains why MySQL’s built‑in utf8 charset cannot store four‑byte characters such as emojis, demonstrates the resulting insert error, shows how switching the database, table and connection to utf8mb4 fixes the issue, and recounts the historical reasons behind MySQL’s limited utf8 implementation.
MySQLcharacter-setemoji
0 likes · 8 min read

This article explains the differences between utf8, utf8mb3 and utf8mb4 character sets in MySQL, demonstrates how utf8mb4 enables full Unicode support including emojis, and provides step‑by‑step SQL examples for creating tables, inserting data, and querying results with the proper character set.
MySQLUnicodeemoji
0 likes · 12 min read

The article explains that MySQL’s legacy “utf8” charset only supports three‑byte characters, causing errors with genuine four‑byte UTF‑8 symbols, and advises all MySQL/MariaDB users to migrate to the proper “utf8mb4” charset using available conversion guides.
MariaDBMySQLcharacter encoding
0 likes · 7 min read


ITPUBMar 19, 2023 · Databases
Upgrading MySQL 5.6/5.7 databases to 8.0 can introduce charset mismatches between existing utf8 (utf8mb3) tables and newly created utf8mb4 tables, causing index loss and performance degradation that can be resolved by unifying the character set across all tables.
MySQLSQLperformance
0 likes · 7 min read

When upgrading MySQL 5.7 tables that use utf8 or utf8mb3 to MySQL 8.0, mismatched character sets and collations can cause index loss and inefficient joins, but converting all tables to utf8mb4 and adjusting the driver table can restore optimal query performance, as demonstrated with detailed examples and profiling results.
CharsetMySQLcollation
0 likes · 7 min read

This article explains why MySQL's built‑in utf8 charset is not true UTF‑8, how inserting 4‑byte emoji characters triggers errors, and why switching the database, tables, and connection to utf8mb4 resolves the issue, along with a brief history of MySQL's encoding decisions.
character encodingemojiutf8mb4
0 likes · 9 min read

This article explains why MySQL's traditional utf8 charset cannot store 4‑byte characters such as emojis, demonstrates the resulting insert errors, and shows how switching the database, system, and column collations to utf8mb4 resolves the issue while also providing a brief history of MySQL's charset implementation.
MySQLSQLcharacter encoding
0 likes · 9 min read

This article explains why MySQL's default utf8 charset cannot store four‑byte characters such as emojis, demonstrates the resulting insertion error, and shows how switching to the utf8mb4 charset resolves the issue while also covering the historical reasons behind MySQL's limited utf8 implementation.
MySQLSQLcharacter-set
0 likes · 8 min read

This article explains why MySQL's default utf8 charset cannot store four‑byte characters like emojis, demonstrates the resulting insert errors, and shows how switching to the utf8mb4 charset resolves the issue while providing a brief history of MySQL's encoding decisions.
MySQLSQLcharacter encoding
0 likes · 8 min read

This article explains why MySQL’s legacy utf8 charset only supports three‑byte characters, causing emoji insertion failures, and shows how switching tables, columns, and the database to utf8mb4 resolves the issue while detailing the historical reasons behind MySQL’s limited utf8 implementation.
MySQLSQLcharacter encoding
0 likes · 9 min read


政采云技术Dec 7, 2021 · Databases
This article examines how MySQL Connector/J determines the character set during connection initialization, explains the transition from UTF8MB3 to UTF8MB4, analyzes source code of versions 5.1.46 and 5.1.47, and provides practical methods to enable UTF8MB4 without upgrading the driver.
Connector/JJavaMySQL
0 likes · 10 min read

The article explains MySQL 5.7's engine‑dependent prefix index length limits, demonstrates how utf8mb4 reduces the maximum indexable column size for MyISAM tables, provides test cases with SQL code, and offers practical solutions such as prefix indexes, composite indexes, and CTAS for large datasets.
MyISAMMySQLPrefix Index
0 likes · 6 min read

This article explains why inserting emoji into MySQL fails with the default utf8 charset, demonstrates how switching to utf8mb4 resolves the issue, and provides a historical overview of MySQL's limited utf8 implementation and the proper use of true UTF‑8 encoding.
MySQLUnicodecharacter-set
0 likes · 7 min read

This article explains the difference between MySQL’s utf8 and utf8mb4 character sets, why utf8 cannot store emojis or complex Chinese characters, and provides step‑by‑step examples showing how to configure tables and columns with utf8mb4 to avoid encoding errors.
MySQLcharacter-setemoji
0 likes · 10 min read

The article explains that MySQL’s legacy “utf8” charset only supports three‑byte characters, causing errors when storing true four‑byte UTF‑8 symbols, and shows how the newer “utf8mb4” charset provides full Unicode support, with historical context and migration guidance.
MariaDBMySQLcharacter-set
0 likes · 7 min read

This article explains MySQL's Unicode character set support, compares the deprecated utf8mb3 with the modern utf8mb4, and provides step‑by‑step SQL commands for safely converting existing databases to the newer charset.
Database MigrationMySQLUnicode
0 likes · 7 min read

This article explains why MySQL's legacy utf8 charset cannot store four‑byte characters such as emoji, demonstrates the resulting insertion error, and shows how switching the database, table, and column collations to utf8mb4 resolves the issue while also covering the historical reasons behind MySQL's limited utf8 implementation.
MySQLcharacter-setemoji
0 likes · 7 min read

This article introduces several MySQL 8 enhancements—including invisible indexes for performance testing, the SET PERSIST command for durable configuration changes, default UTF8MB4 encoding, Common Table Expressions for clearer queries, and window functions for ranking and aggregation—illustrated with practical SQL examples.
CTEMySQLWindow Functions
0 likes · 6 min read

This article examines common MySQL pitfalls—including signed vs. unsigned integers, auto‑increment key requirements, varchar length versus byte count, case‑insensitive collations, and storing emoji characters—providing concrete SQL examples, error screenshots, and configuration tips to help developers avoid unexpected errors.
Database DesignMySQLSQL
0 likes · 9 min read

The article explains why MySQL’s built‑in utf8 charset only supports up to three‑byte characters, causing insert errors with four‑byte emojis, and shows how switching tables, system, and connection settings to utf8mb4 resolves the issue while detailing the historical reasons behind this limitation.
character-setdatabase encodingemoji
0 likes · 9 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

The article explains that MySQL’s legacy “utf8” character set only supports three‑byte sequences and therefore cannot store true UTF‑8 characters, describes the historical reasons behind this limitation, and advises all MySQL/MariaDB users to migrate to the proper utf8mb4 charset.
MariaDBMySQLcharacter-set
0 likes · 12 min read

The article explains why MySQL’s legacy “utf8” character set only supports three‑byte sequences, causing errors with genuine four‑byte UTF‑8 characters, and shows how the proper “utf8mb4” charset resolves the issue, including historical background, practical examples, and migration guidance.
MariaDBMySQLUnicode
0 likes · 10 min read

This article explains MySQL character sets and collations, describes common character sets such as latin1, utf8mb3, utf8mb4 and gb18030, shows how to query available sets and collations, compares PAD SPACE and NO PAD behavior, and provides step‑by‑step migration examples between utf8, utf8mb3 and utf8mb4.
MySQLcharacter-setcollation
0 likes · 12 min read


ITPUBJan 7, 2020 · Databases
The article explains that MySQL’s legacy “utf8” charset only supports three‑byte characters, causing errors when storing true four‑byte UTF‑8 data, and shows how switching to the proper “utf8mb4” charset resolves the issue.
MariaDBMySQLcharacter-set
0 likes · 8 min read

This article explains why MySQL 8.0 switched its default character set to utf8mb4 and provides two detailed migration plans—including configuration changes, data export/import, table and column conversion, and post‑migration testing—to help users safely upgrade their databases.
MySQLSQLcharset migration
0 likes · 6 min read

The article explains why MySQL's legacy "utf8" charset only supports three‑byte characters, causing storage errors for true four‑byte UTF‑8 symbols, and advises developers to migrate all MySQL/MariaDB databases to the proper "utf8mb4" charset.
MariaDBMySQLcharacter encoding
0 likes · 7 min read


ITPUBOct 10, 2019 · Databases
The article explains that MySQL’s legacy “utf8” charset only supports three‑byte characters, causing errors when storing true four‑byte UTF‑8 symbols like emojis, and shows why switching to the proper “utf8mb4” charset is essential for correct Unicode handling.
MariaDBMySQLUnicode
0 likes · 8 min read


21CTOMay 13, 2019 · Databases
Discover why MySQL’s legacy ‘utf8’ charset only supports three‑byte characters, causing storage errors for true UTF‑8 data, and learn how switching to the proper ‘utf8mb4’ charset resolves these issues, with a brief history and practical migration guidance.
MariaDBMySQLUTF-8
0 likes · 7 min read

This article explains why MySQL’s legacy "utf8" charset only supports three‑byte characters, why it’s not true UTF‑8, and provides a clear guide to migrating databases to the proper "utf8mb4" charset for full Unicode support.
MariaDBMySQLUnicode
0 likes · 8 min read


ITPUBJul 21, 2017 · Databases
This article explains why MySQL throws "Incorrect string value" when storing emojis, how utf8mb4 solves the problem, and provides step‑by‑step instructions—including table conversion, my.cnf changes, connector upgrades, and runtime workarounds—for reliable emoji storage.
JDBCMyBatisMySQL
0 likes · 7 min read
