Changes between Version 24 and Version 25 of MySqlDb

Timestamp:

Sep 12, 2008, 6:49:19 PM (16 years ago)

Author:

Christian Boos

Comment:

the utf8_bin collation type advice is for 0.11.1 and up, fixes #7626

MySqlDb

@@ -3 +3 @@
  ''It is somewhat supported by Trac since 0.10, but there are some limitations (see [#KnownIssues]). Use this only if you don't have other choice, and be warned that there can be many issues, in particular related to the unicode support and the repository cache support. Some users are nevertheless using MySQL successfully, so it ''might'' work for you. The primary supported backends though are PostgreSQL and SQLite.''
 
-Starting with [milestone:0.10] Trac can use MySQL for its DatabaseBackend, but consider using at least [milestone:0.10.4], [milestone:0.10.5]dev or [milestone:0.11]dev.
+Starting with [milestone:0.10] Trac can use MySQL for its DatabaseBackend, but consider using at least [milestone:0.10.5] or, much better, [milestone:0.11.1].
 
 
 == Requirements ==
 === MySQL ===
+
+ '' '''Warning:''' 
+ The following applies to Trac starting with [milestone:0.11.1]. [[br]]
+ For earlier versions of Trac, please see MySqlDb@22#MySQL. [[br]]
+ In short, up to 0.11 use ''utf8_general_ci'' collation type, but starting with 0.11.1, use ''utf_bin'' as explained below.''
 
 In order to avoid several issues with unicode and international characters throughout Trac (e.g., international characters turning into question marks with mysterious "Incorrect string value" errors logged), we '''''strongly''''' advise MySQL users to only use databases having the ''`utf8`'' character set and the ''`utf8_bin`'' collation type. However, changing collation to ''utf8'' makes MySQL fail in 4.1.x and 5.0.x versions on MyISAM table type, because some Trac tables indexes become "too big". This will be (hopefully) addressed in [milestone:0.10.4]. As a workaround it has been [comment:ticket:3659:5 recommended] to use InnoDB tables instead of MyISAM where this limitation is absent.