diff options
| author | Matt Lauber <github@mklauber.com> | 2014-04-21 10:48:33 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-04-21 13:21:14 -0400 |
| commit | ca3927dfb946cf7de2fbd1d85ce9433f02069eba (patch) | |
| tree | 04f78ad6222f4e5458b8e04ccf1ed5ab72e8b28f | |
| parent | 83420e70ef98c015207f8a49bd35ebb098ac6df5 (diff) | |
[1.4.x] Corrected the section identifier for MySQL unicode reference.
Backport of b2514c02e1 from master
| -rw-r--r-- | docs/ref/unicode.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index 1286dcfdd0..4d644cd68a 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 21.2.2 in |