Changes between Version 47 and Version 48 of MySqlDb

Timestamp:

Feb 5, 2010, 12:53:19 PM (14 years ago)

Author:

anatoly techtonik <techtonik@…>

Comment:

update information about how to test DB collations

MySqlDb

@@ -18 +18 @@
 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.
+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]).
 
-A proper database can be created with the MySQL monitor, like this:
+A proper database can be created with any MySQL client, like this:
 {{{
 CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin; 
@@ -31 +31 @@
 mysql> USE trac;
 Database changed
-mysql> SHOW VARIABLES LIKE '%character%';
-+--------------------------+--------------------
-| Variable_name            | Value
-+--------------------------+--------------------
-| character_set_client     | cp1251
-| character_set_connection | cp1251
-| character_set_database   | utf8
-| character_set_filesystem | binary
-| character_set_results    | cp1251
-| character_set_server     | utf8
-| character_set_system     | utf8
-| character_sets_dir       | C:\DevServer\Instal
-+--------------------------+--------------------
-8 rows in set (0.00 sec)
+mysql> SHOW VARIABLES WHERE variable_name IN ('character_set_database', 'collation_database');
++------------------------+----------+
+| Variable_name          | Value    |
++------------------------+----------+
+| character_set_database | utf8     |
+| collation_database     | utf8_bin |
++------------------------+----------+
+2 rows in set (0.01 sec)
+
 mysql>
+}}}
+
+If you are setting new collation on old database, make sure that columns are converted too:
+{{{
+mysql> SHOW FULL COLUMNS FROM `node_change`;
++-------------+-------------+-----------+-
+| Field       | Type        | Collation | 
++-------------+-------------+-----------+-
+| rev         | varchar(64) | utf8_bin  | 
+| path        | text        | utf8_bin  | 
+| node_type   | varchar(32) | utf8_bin  | 
+| change_type | varchar(32) | utf8_bin  | 
+| base_path   | text        | utf8_bin  | 
+| base_rev    | varchar(64) | utf8_bin  | 
++-------------+-------------+-----------+-
+6 rows in set (0.00 sec)                  
 }}}