Learn how to prevent six frequent MySQL problems—including index misuse, transaction isolation anomalies, inefficient pagination, charset and collation errors, risky foreign-key cascades, and misconfigured connection pools—through detailed explanations, code examples, and practical mitigation strategies.
This article explains why altering a column length in OceanBase may trigger an "Alter charset or collation type not supported" error, analyzes the underlying charset and collation settings, and provides a solution that explicitly specifies charset and collation to ensure successful column expansion across versions.
This article dives deep into MySQL's charset and collation system, explaining concepts, configuration levels, system variables, string literals, conversion rules, Unicode sorting algorithms, binary collations, and practical tips to avoid common encoding pitfalls and ensure correct string handling.
This article explains common scenarios of implicit type and charset conversions in MySQL, demonstrates how they cause index loss and performance degradation through detailed examples and EXPLAIN output, and provides practical guidelines to prevent such conversions in production environments.
This article explores the true maximum length of MySQL VARCHAR columns, showing how charset, NULLability, column count, and row format affect the limit, and explains the underlying storage mechanics, row overflow, and alternatives for data larger than 64 KB.
This article debunks the common belief that MySQL VARCHAR can store up to 65535 characters, showing how the true limit depends on the chosen character set, NULLability, column count, and row‑format details, and explains how oversized values are stored or require TEXT/BLOB types.
The article analyzes why a sed command freezes while modifying a MySQL MHA installation script on a CentOS 6 system, identifies the charset conversion issue caused by GBK locale and missing spaces after comment symbols, and provides a step‑by‑step debugging and fix procedure.
This article investigates the true maximum length of MySQL VARCHAR columns, showing how charset byte size, NULLability, column count, and the InnoDB Dynamic row format together determine the effective limit, and explains how overflow is handled for very large strings.
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.
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.
This article explains why Chinese characters often appear as garbled text when crawling websites with Python and provides three practical solutions—using response.content, manually setting the response encoding, and applying a generic encode‑decode trick—to reliably decode the data.
This article experimentally determines the maximum number of characters a MySQL 5.7 VARCHAR column can hold under different character sets, explains the underlying row‑size and index‑key restrictions, and provides concrete CREATE TABLE examples for latin1, utf8, and utf8mb4.
A MySQL join between a large and a small table ran for seconds because differing character sets forced implicit conversions that disabled the index, and the article shows how to diagnose the issue with EXPLAIN, fix it by aligning charsets, and avoid similar pitfalls.
A sysbench benchmark comparing MySQL 5.7.25 and MySQL 8.0.15 shows that latin1 charset favors 5.7, while utf8mb4 dramatically improves 8.0 performance, and that collations such as utf8mb4_unicode_ci can further affect query speed.
This article walks through diagnosing a MySQL crash, using innodb_force_recovery to start the server, exporting the data with mysqldump, handling charset mismatches, importing into a new instance, and restoring normal operation while offering best‑practice backup recommendations.
This article explains why MySQL queries can become case‑insensitive, describes how collations and character sets control case sensitivity, and presents three practical solutions—changing the collation, converting column types, and using binary or collate clauses in queries—to achieve case‑sensitive behavior.
This article compiles ten classic MySQL error scenarios—from connection limits and replication conflicts to charset issues and file‑open limits—explaining the root causes, diagnostic commands, and step‑by‑step solutions so beginners and seasoned DBAs can troubleshoot confidently.
A front‑end login slowdown was traced to a MySQL UPDATE that ran for 40 seconds because a varchar column’s charset conversion forced a full‑table scan, and the article walks through the logs, tests, and the fix of unifying the column charset to UTF‑8.
This article explains how computers store and display characters using binary, defines character sets and encodings such as ASCII, GB2312, GBK, GB18030, BIG5 and Unicode, compares UTF‑8, UTF‑16, UTF‑32, and describes related HTTP headers like Accept‑Charset, Content‑Type, and Content‑Encoding.
