summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAdrian Holovaty <adrian@holovaty.com>2008-09-10 03:57:52 +0000
committerAdrian Holovaty <adrian@holovaty.com>2008-09-10 03:57:52 +0000
commit1aa8449fb718875289fff179845503dd8c9684ce (patch)
treea9a521e302996374c65023afa2331ff757191e64 /docs
parent568b8637bfecc74906282f26fcfef16a0cb0d156 (diff)
Fixed #9003 -- Fixed awkward wording in querysets.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8996 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/querysets.txt13
1 files changed, 6 insertions, 7 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 68b69b6603..ef3470e12e 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -865,13 +865,12 @@ SQL equivalents::
.. admonition:: MySQL comparisons
- In MySQL, whether or not ``exact`` comparisons are case-insensitive by
- default. This is controlled by the collation setting on the database
- tables (this is a database setting, *not* a Django setting). It is
- possible to configured you MySQL tables to use case-sensitive comparisons,
- however there are some trade-offs involved. For more information about
- this, see the :ref:`collation section <mysql-collation>` in the
- :ref:`databases <ref-databases>` documentation.
+ In MySQL, a database table's "collation" setting determines whether
+ ``exact`` comparisons are case-sensitive. This is a database setting, *not*
+ a Django setting. It's possible to configure your MySQL tables to use
+ case-sensitive comparisons, but some trade-offs are involved. For more
+ information about this, see the :ref:`collation section <mysql-collation>`
+ in the :ref:`databases <ref-databases>` documentation.
iexact
~~~~~~