mirror of
https://github.com/django/django.git
synced 2025-10-24 06:06:09 +00:00
Updated MySQL links to version 5.6.
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user