Changes between Version 44 and Version 45 of MySqlDb

Timestamp:

Aug 28, 2009, 12:42:16 AM (15 years ago)

Author:

dukman821@…

Comment:

Updated a sentence for grammar so it flows better.

MySqlDb

@@ -20 +20 @@
 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]).
+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]).
 
-Proper database can be created with the MySQL monitor, like that:
+A proper database can be created with the MySQL monitor, like this:
 {{{
 CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin; 
 }}}
 
-To check character set settings for your database, issue command:
+To check character set settings for your database, issue the following commands:
 {{{
 mysql> USE trac;