Skip to content
Browse files

[1.0.X] Fixed #11417 -- Corrected typo in MySQL collation notes. Than…

…ks to vorushin for the report.

Merge of r11169 from trunk.


git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.0.X@11171 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent df2011c commit c05f4d5a220d6dc83c5b68f3beb5fb3b49d30d29 @freakboy3742 freakboy3742 committed
Showing with 1 addition and 1 deletion.
  1. +1 −1 docs/ref/databases.txt
View
2 docs/ref/databases.txt
@@ -167,7 +167,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
MySQLdb 1.2.1p2, you should still use ``utf8_collation_ci_swedish`` (the
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
``django_admin_log``). Those are the two standard tables that use
:class:`~django.db.model.TextField` internally.

0 comments on commit c05f4d5

Please sign in to comment.
Something went wrong with that request. Please try again.