Changes between Version 30 and Version 31 of MySqlDb

Timestamp:

Mar 4, 2009, 11:05:29 PM (15 years ago)

Author:

anatoly techtonik <techtonik@…>

Comment:

+ query to get engine type

MySqlDb

@@ -16 +16 @@
 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]).
 
-Such databases can be created with the MySQL monitor, like that:
+Proper database can be created with the MySQL monitor, like that:
 {{{
 CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin; 
@@ -94 +94 @@
 
 ==== MyISAM to InnoDB ====
+Check that tables are not already converted:
+{{{
+SELECT table_name, engine FROM information_schema.tables WHERE table_schema=DATABASE();
+}}}
 
 For every table in Trac database issue: