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:20:51 -0400 |
| commit | 25adac9b42e65caa5d2d42b6322e59ffb48df775 (patch) | |
| tree | cd33c50fd614357b7406f02845ab92a33f822fb9 | |
| parent | 1b43131b5d65060a7e067fbf6167517c559d2807 (diff) | |
[1.6.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 c9534c12c9..96a0e170ff 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 |