Edgewall Software

Changes between Version 68 and Version 69 of MySqlDb


Ignore:
Timestamp:
May 2, 2015, 6:48:06 PM (9 years ago)
Author:
figaro
Comment:

Added Percona drop-in replacement

Legend:

Unmodified
Added
Removed
Modified
  • MySqlDb

    v68 v69  
    11[[PageOutline(2-3)]]
     2
    23= MySQL and its MySQLdb Python bindings
    34
     
    1213 For earlier versions of Trac, please see MySqlDb@22#MySQL. ''
    1314
    14 The recommended versions of MySQL are those from 5.x series. The [http://askmonty.org/wiki/index.php/MariaDB MariaDB] variant of MySQL works as well, tested MariaDB 5.3.3, MySQLdb 1.2.3 and Trac 0.12.3.
     15The recommended versions of MySQL are those from 5.x series.
    1516
    16 In order to avoid Unicode and international characters problems in Trac, eg 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.
     17The following MySQL dropin replacements are also known to work:
     18 * The [http://askmonty.org/wiki/index.php/MariaDB MariaDB] variant: tested MariaDB 5.3.3, MySQLdb 1.2.3 and Trac 0.12.3.
     19 * The [http://www.percona.com/software/percona-server/ps-5.6 Percona] variant: tested Percona 5.6 with Trac 1.1.4.
    1720
    18 Also, all tables MUST be created as  **InnoDB** or **TokuDB** 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]. Be aware that the cluster storage engine NDB introduces some limits for Trac (#8567).
     21In order to avoid Unicode and international characters problems in Trac, eg 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.
     22
     23Also, all tables '''must''' be created as **InnoDB** or **TokuDB** 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]. Be aware that the cluster storage engine NDB introduces some limits for Trac (#8567).
    1924
    2025A proper database can be created with any MySQL client, like this:
     
    8287Older versions can be found at the [https://sourceforge.net/projects/mysql-python/ mysql-python] Sourceforge project:
    8388|| '''Version''' || '''Notes''' ||
     89|| `MySQL-python-1.2.2b2` ||  Was [googlegroups:trac-users:e291b3ecb4a990a1 reported] to solve an `AttributeError: 'array.array' object has no attribute 'startswith'` error seen when viewing a changeset. These problems ought to be fixed in 1.2.2b3; if they are not, or if you have other issues, please file a bug in the [https://sourceforge.net/tracker/?group_id=22307&atid=374932 MySQL-python Bug Tracker] ||
    8490|| `MySQL-python 1.2.1_p2` || This was the previously recommended version -- **unsupported** ||
    8591|| `MySQL-python 1.2.0-3.2.2`, `MySQL-python 1.2.2b2` || Reported to have issues (see #3645) -- **unsupported** ||
    86 || `MySQL-python-1.2.2b2` ||  Was [googlegroups:trac-users:e291b3ecb4a990a1 reported] to solve an `AttributeError: 'array.array' object has no attribute 'startswith'` error seen when viewing a changeset. These problems ought to be fixed in 1.2.2b3; if they are not, or if you have other issues, please file a bug in the [https://sourceforge.net/tracker/?group_id=22307&atid=374932 MySQL-python Bug Tracker] ||
    8792
    8893On FreeBSD this package is called {{{py-MySQLdb}}} in [http://www.freshports.org/databases/py-MySQLdb55/ the ports collection].