Edgewall Software

Changes between Version 20 and Version 21 of SqLiteToMySql


Ignore:
Timestamp:
May 26, 2015, 8:39:00 PM (9 years ago)
Author:
Ryan J Ollos
Comment:

Drop section that pertained to ​SqliteToMySqlScript.

Legend:

Unmodified
Added
Removed
Modified

  • SqLiteToMySql

    v20 v21  
    11= Convert Trac DB, from SQLite to MySQL
    22
    3 The easiest way to convert a Trac SQLite database to a MySQL database is as follows:
     3**Note:** You can also use [TracHacks:TracMigratePlugin] as a conversion tool.
     4
     5You can convert a Trac SQLite database to a MySQL database as follows:
    46
    57{{{
    … …  
    9597----
    9698One alternative to dropping the reports is to log into trac as a privileged user that can edit the reports, call up one report after the other, click on EDIT and look out for {{{CAST(p.value AS int)}}}. Change this to {{{CAST(p.value AS unsigned)}}} and it should work. This might be easier than recreating all your custom reports.
    97 ----
    98 
    99 You can also use [TracHacks:TracMigratePlugin] as a conversion tool.
    100 
    101 The only issues you might run into are with character collation on your database. With the default latin1 character set and latin1 collation, `/path/to/file` and `/path/to/FILE` are identical, potentially causing index collisions. Therefore create your database with UTF8 binary collation '''and''' set the server's default table type to InnoDB:
    102 
    103  * in my.cnf:
    104 {{{
    105 [mysqld]
    106 default-table-type = InnoDB
    107 }}}
    108 
    109  * in the mysql client:
    110 {{{
    111 CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;
    112 }}}
    113 
    114 Also, look at ticket:6986 to significantly improve Trac performance with MySQL.
    115 
    116 ----
    11799
    118100This page contains a summarised procedure: http://www.pokesoft.net/blog/?p=473