Changes between Version 31 and Version 32 of MySqlDb

Timestamp:

Mar 5, 2009, 12:37:13 AM (15 years ago)

Author:

anonymous

Comment:

remove outdated references

MySqlDb

@@ -2 +2 @@
 
  ''The primary supported backends are PostgreSQL and SQLite. MySQL is supported by Trac since 0.10 with limitations (see [#KnownIssues]). Use this only if you don't have other choice, and be warned that there can be issues unicode support and the repository cache. Some users are nevertheless using MySQL successfully, so it ''might'' work for you. ''
-
-Recommended Trac for using with MySQL DatabaseBackend is [milestone:0.10.5] or, much better, [milestone:0.11.1].
-
 
 == Requirements ==
@@ -11 +8 @@
  '' '''Warning:''' 
  The following applies to Trac starting with [milestone:0.11.1]. [[br]]
- For earlier versions of Trac, please see MySqlDb@22#MySQL. [[br]]
- In short, up to 0.11 use ''utf8_general_ci'' collation type, but starting with 0.11.1, use ''utf_bin'' as explained below.''
+ For earlier versions of Trac, please see MySqlDb@22#MySQL.
 
 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]).
@@ -20 +16 @@
 CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin; 
 }}}
-
-Some unicode related MySQL-python bugs were worked around in r7286 so if you're experiencing problems with non-ascii text you should consider upgrading to Trac 0.11.1.
 
 To check character set settings for your database, issue command:
@@ -116 +110 @@
 
 ==== From SQLite ====
-While a more robust method may be created for [milestone:0.10.4] to allow easy conversion from SQLite to MySQL, users have reported success with the [wiki:SqLiteToMySql following method].
+Users have reported success with the [wiki:SqLiteToMySql following method].