diff options
| author | Tim Graham <timograham@gmail.com> | 2014-08-02 10:27:01 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-08-02 10:27:01 -0400 |
| commit | fb4f3e04b13681c5ec4cbf37d280ffebc887d620 (patch) | |
| tree | 9454b59481d72c063c65c67181b393740eed8bb6 /docs/ref/unicode.txt | |
| parent | de0a22be35bbe6f23d826bcc9aa27756ffe59e8c (diff) | |
Updated MySQL links to version 5.6.
Diffstat (limited to 'docs/ref/unicode.txt')
| -rw-r--r-- | docs/ref/unicode.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt index 9f10d5a43a..90201d2d33 100644 --- a/docs/ref/unicode.txt +++ b/docs/ref/unicode.txt @@ -17,8 +17,8 @@ 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 10.1.3.2 for MySQL 5.1) - for details on how to set or alter the database character set encoding. +* MySQL users, refer to the `MySQL manual`_ 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 PostgreSQL 9) for details on creating databases with the correct encoding. @@ -26,7 +26,7 @@ able to store certain characters in the database, and information will be lost. * SQLite users, there is nothing you need to do. SQLite always uses UTF-8 for internal encoding. -.. _MySQL manual: http://dev.mysql.com/doc/refman/5.1/en/charset-database.html +.. _MySQL manual: http://dev.mysql.com/doc/refman/5.6/en/charset-database.html .. _PostgreSQL manual: http://www.postgresql.org/docs/current/static/multibyte.html All of Django's database backends automatically convert Unicode strings into |