Changes between Version 66 and Version 67 of MySqlDb

Timestamp:

Feb 18, 2015, 8:01:28 AM (9 years ago)

Author:

Jun Omae

Comment:

Unit and functional tests pass with TokuDB.

MySqlDb

@@ -16 +16 @@
 In order to avoid Unicode and international characters problems in Trac, eg 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.
 
-Also, all tables MUST be created as  '''InnoDB''' type tables, because Trac uses a transaction mechanism that is 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]. Be aware that the cluster storage engine NDB introduces some limits for Trac (#8567).
+Also, all tables MUST be created as  **InnoDB** or **TokuDB** type tables, because Trac uses a transaction mechanism that is 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]. Be aware that the cluster storage engine NDB introduces some limits for Trac (#8567).
 
 A proper database can be created with any MySQL client, like this: