innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #11417 -- Corrected typo in MySQL collation notes. Thanks to vorushin for the report. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11169 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2009-07-03 07:15:48 +00:00
parent 037b833f2e
commit b73319ae7b
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/databases.txt
View File

@ -220,7 +220,7 @@ bytestrings (which shouldn't be too difficult) is the recommended solution.
Should you decide to use ``utf8_bin`` collation for some of your tables with Should you decide to use ``utf8_bin`` collation for some of your tables with
MySQLdb 1.2.1p2, you should still use ``utf8_collation_ci_swedish`` (the MySQLdb 1.2.1p2, you should still use ``utf8_collation_ci_swedish`` (the
default) collation for the :class:`django.contrib.sessions.models.Session` default) collation for the :class:`django.contrib.sessions.models.Session`
table (usually called ``django_session`` and the table table (usually called ``django_session``) and the
:class:`django.contrib.admin.models.LogEntry` table (usually called :class:`django.contrib.admin.models.LogEntry` table (usually called
``django_admin_log``). Those are the two standard tables that use ``django_admin_log``). Those are the two standard tables that use
:class:`~django.db.model.TextField` internally. :class:`~django.db.model.TextField` internally.