Changes between Version 12 and Version 13 of MySqlDb

Timestamp:

Mar 20, 2007, 8:06:43 PM (17 years ago)

Author:

techtonik <techtonik@…>

Comment:

state the reason why utf8 Trac doesn't work with MySQL 4.1.x

MySqlDb

@@ -3 +3 @@
  ''work in progress, only the most critical information is there for now''
 
-Starting with [milestone:0.10] Trac can use MySQL for its DatabaseBackend.
+Starting with [milestone:0.10] Trac can use MySQL for its DatabaseBackend, but only starting with [milestone:0.10.4] will MySQL be fully supported (at least that's the plan). So stick to [milestone:0.10.3] for now.
 
-Well, sort of.
-
-Better is to use [milestone:0.10.3], and only starting with [milestone:0.10.4] will MySQL be fully supported (at least that's the plan).
 
 == Requirements ==
 === MySQL ===
 
-In order to avoid several issues related to the use of unicode characters throughout Trac, we '''''strongly''''' advise MySQL users to only use databases having the ''`utf8`'' character set and the ''`utf8_general_ci`'' collation type.
+In order to avoid several issues with unicode and international characters throughout Trac, we '''''strongly''''' advise MySQL users to only use databases having the ''`utf8`'' character set and the ''`utf8_general_ci`'' collation type. However, some of Trac indexes in utf8 are incompatible with MySQL 4.1.x, so anything before MySQL 5.0.x will just not work in this configuration.
 
 Such databases can be created with the MySQL monitor, like that: