Fixed #9003 -- Fixed awkward wording in querysets.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8996 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
568b8637bf
commit
1aa8449fb7
|
@ -865,13 +865,12 @@ SQL equivalents::
|
||||||
|
|
||||||
.. admonition:: MySQL comparisons
|
.. admonition:: MySQL comparisons
|
||||||
|
|
||||||
In MySQL, whether or not ``exact`` comparisons are case-insensitive by
|
In MySQL, a database table's "collation" setting determines whether
|
||||||
default. This is controlled by the collation setting on the database
|
``exact`` comparisons are case-sensitive. This is a database setting, *not*
|
||||||
tables (this is a database setting, *not* a Django setting). It is
|
a Django setting. It's possible to configure your MySQL tables to use
|
||||||
possible to configured you MySQL tables to use case-sensitive comparisons,
|
case-sensitive comparisons, but some trade-offs are involved. For more
|
||||||
however there are some trade-offs involved. For more information about
|
information about this, see the :ref:`collation section <mysql-collation>`
|
||||||
this, see the :ref:`collation section <mysql-collation>` in the
|
in the :ref:`databases <ref-databases>` documentation.
|
||||||
:ref:`databases <ref-databases>` documentation.
|
|
||||||
|
|
||||||
iexact
|
iexact
|
||||||
~~~~~~
|
~~~~~~
|
||||||
|
|
Loading…
Reference in New Issue