From 0bd913a19cf0e7515834d6cb6d9e668840fecce5 Mon Sep 17 00:00:00 2001 From: Matt Lauber Date: Mon, 21 Apr 2014 10:48:33 -0400 Subject: [PATCH] [1.7.x] Corrected the section identifier for MySQL unicode reference. Backport of b2514c02e1 from master --- docs/ref/unicode.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index 306a2dfb48..43401de65c 100644 --- a/docs/ref/unicode.txt +++ b/docs/ref/unicode.txt @@ -17,7 +17,7 @@ data. Normally, this means giving it an encoding of UTF-8 or UTF-16. If you use a more restrictive encoding -- for example, latin1 (iso8859-1) -- you won't be able to store certain characters in the database, and information will be lost. -* MySQL users, refer to the `MySQL manual`_ (section 9.1.3.2 for MySQL 5.1) +* MySQL users, refer to the `MySQL manual`_ (section 10.1.3.2 for MySQL 5.1) for details on how to set or alter the database character set encoding. * PostgreSQL users, refer to the `PostgreSQL manual`_ (section 22.3.2 in