| commit | 371cc04f337b934f2ea7700f0ea596353c1d5e90 | |
| author | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Tue, 26 Aug 2008 01:59:25 +0000 (26 01:59 +0000) | ||
| committer | mtredinnick <mtredinnick@bcc190cf-cafb-0310-a4f2-bffc1f526a37> | |
| Tue, 26 Aug 2008 01:59:25 +0000 (26 01:59 +0000) | ||
| tree | 26840b0a9eeea4d1f1150a41cc9900fddd8e1edd | treesnapshot (tar.gz zip) |
| parent | 8720ecb327425956dca8d5eb02128568febb9552 | commitdiff |
Added documentation to explain the gains and losses when using utf8_bin
collation in MySQL. This should help people to make a reasonably informed
decision. Usually, leaving the MySQL collation alone will be the best solution,
but if you must change it, this gives a start to the information you need and
pointers to the appropriate place in the MySQL docs.
There's a small chance I also got all the necessary Sphinx markup correct, too
(it builds without errors, but I may have missed some chances for glory and
linkage).
Fixed #2335, #8506.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8568 bcc190cf-cafb-0310-a4f2-bffc1f526a37
collation in MySQL. This should help people to make a reasonably informed
decision. Usually, leaving the MySQL collation alone will be the best solution,
but if you must change it, this gives a start to the information you need and
pointers to the appropriate place in the MySQL docs.
There's a small chance I also got all the necessary Sphinx markup correct, too
(it builds without errors, but I may have missed some chances for glory and
linkage).
Fixed #2335, #8506.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@8568 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| docs/ref/databases.txt | diffblobblamehistory | |
| docs/ref/models/fields.txt | diffblobblamehistory | |
| docs/ref/models/querysets.txt | diffblobblamehistory |