Changes between Version 14 and Version 15 of MySqlDb

Timestamp:

Apr 3, 2007, 9:36:48 AM (17 years ago)

Author:

techtonik <techtonik@…>

Comment:

+ problem with 'too big' unicode indexes and MyISAM tables is actual for all databases

MySqlDb

@@ -9 +9 @@
 === MySQL ===
 
-In order to avoid several issues with unicode and international characters throughout Trac, we '''''strongly''''' advise MySQL users to only use databases having the ''`utf8`'' character set and the ''`utf8_general_ci`'' collation type. However, prior to [milestone:0.10.4] some of Trac indexes in ''utf8'' are incompatible with MySQL 4.1.x (too big), so anything before MySQL 5.0.x just will not work in this configuration.
+In order to avoid several issues with unicode and international characters throughout Trac, we '''''strongly''''' advise MySQL users to only use databases having the ''`utf8`'' character set and the ''`utf8_general_ci`'' collation type. However, changing collation to ''utf8'' makes MySQL fail in 4.1.x and 5.0.x versions on MyISAM table type, because some Trac tables indexes become "too big". This will be (hopefully) addressed in [milestone:0.10.4]. As a workaround it has been [comment:ticket:3659:5 recommended] to use InnoDB tables instead of MyISAM where this limitation is absent.
 
 Such databases can be created with the MySQL monitor, like that:
@@ -16 +16 @@
 }}}
 
-To check what are the settings for your database, issue command:
+To check character set settings for your database, issue command:
 {{{
-mysql> USE TRAC;
+mysql> USE trac;
 Database changed
 mysql> SHOW VARIABLES LIKE '%character%';
@@ -38 +38 @@
 
 See also #3884.
-
-It has also been [comment:ticket:3659:5 recommended] to use InnoDB instead of MyISAM tables, though it's not completely clear at this point if this really helps. [http://dev.mysql.com/doc/refman/5.0/en/innodb-overview.html InnoDB] provides referential integrity
-and transactions, so this should help.
 
 === MySQLdb ===