id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
22458	MySQL notes recommend legacy utf8_general_ci unicode collation	tobami@…	mardini	"The documentation section ""MySQL notes"" recommends the obsolete utf8_general_ci collation settings:
""By default, with a UTF-8 database, MySQL will use the utf8_general_ci collation."" [0]
and
""... you should still use utf8_general_ci (the default) collation for the django.contrib.sessions.models.Session table""

While it may still be the default depending on your MySQL version, MySQL itself recommends utf8_unicode_ci instead of utf8_general_ci, as the later can be incorrect for some characters and languages and its performance benefits are no longer relevant. From the MySQL docs themselves:
""utf8_general_ci is a legacy collation that does not support expansions, contractions, or ignorable characters."" [1]

Using utf8_general_ci can be the cause of difficult to debug text issues.
IMO Django should update its MySQL collation recommendation to utf8_unicode_ci.

[0] https://docs.djangoproject.com/en/dev/ref/databases/#collation-settings
[1] http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-sets.html"	Cleanup/optimization	closed	Documentation	1.7-beta-1	Normal	fixed	unicode		Accepted	0	0	0	0	1	0