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:19:46 -0400 |
| commit | b2514c02e186662ab82b77106a1a85abecf94039 (patch) | |
| tree | e1a297c51936a0bb902f8bf0d1deb35a891026b6 /docs/ref/unicode.txt | |
| parent | c54e7ec9ca1417bee0409489ed12f3e0f942a784 (diff) | |
Corrected the section identifier for MySQL unicode reference.
Diffstat (limited to 'docs/ref/unicode.txt')
| -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 d8581e801c..9f10d5a43a 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 |