Changes between Version 40 and Version 41 of MySqlDb

Timestamp:

May 11, 2009, 9:20:27 PM (15 years ago)

Author:

Christian Boos

Comment:

#MySQL requirements: replaced emphasis by the more direct "MUST" imperative form

MySqlDb

@@ -16 +16 @@
  For earlier versions of Trac, please see MySqlDb@22#MySQL. ''
 
-To avoid unicode and international characters problems in Trac (e.g., international characters turning into question marks with mysterious "Incorrect string value" errors logged), we '''''strongly''''' advise MySQL users to use only databases with the ''`utf8`'' character set and the ''`utf8_bin`'' collation type. All tables should be created as  '''InnoDB''' or '''NDB''' type tables, because Trac uses transaction mechanism that not supported by MyISAM tables (see [comment:ticket:8067:5] and [http://dev.mysql.com/tech-resources/articles/storage-engine/part_3.html MySQL docs]).
+The recommended versions of MySQL are those from 5.0.x series.
+It might work with 4.1.x or 6.0.x, but no guarantees.
+It seems that some users were using the [http://askmonty.org/wiki/index.php/MariaDB MariaDB] variant of MySQL, but again, no guarantees.
+
+To avoid unicode and international characters problems in Trac (e.g., international characters turning into question marks with mysterious "Incorrect string value" errors logged), the Trac database MUST be configured  with the ''`utf8`'' character set and the ''`utf8_bin`'' collation type. All tables MUST be created as  '''InnoDB''' or '''NDB''' type tables, because Trac uses transaction mechanism that not supported by MyISAM tables (see [comment:ticket:8067:5] and [http://dev.mysql.com/tech-resources/articles/storage-engine/part_3.html MySQL docs]).
 
 Proper database can be created with the MySQL monitor, like that:
@@ -56 +60 @@
 }}}
 
-Note that it seems that some users were using the [http://askmonty.org/wiki/index.php/MariaDB MariaDB] variant of MySQL with some success(?).
 
 === MySQLdb ===