Changes between Version 51 and Version 52 of MySqlDb

Timestamp:

Apr 26, 2010, 2:45:00 PM (14 years ago)

Author:

Christian Boos

Comment:

emphasize the Incorrect string value error and the way to fix it

MySqlDb

@@ -20 +20 @@
 Some users reported that [http://askmonty.org/wiki/index.php/MariaDB MariaDB] variant of MySQL works as well, 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 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]).
+In order 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.
+
+Besides, all tables MUST be created as  '''InnoDB''' or '''NDB''' 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]).
 
 A proper database can be created with any MySQL client, like this:
@@ -42 +44 @@
 mysql>
 }}}
+
+If this is not the case (e.g. you have `latin1`/`latin1_swedish_ci` or even `utf8` but `utf8_ci` collation), then read on to the [#Collationfromwhatevertoutf8_bin] section below to see how to change it. 
 
 If you are setting new collation on old database, make sure that column collations are converted too: