Convert Trac DB, from SQLite to MySQL

Note: You can also use ​TracMigratePlugin as a conversion tool.

You can convert a Trac SQLite database to a MySQL database as follows:

% echo ".dump" | sqlite3 trac.db > trac.sql
% mysql tracdb < trac.sql

There could be syntax errors that have to be manually fixed in the file trac.sql.

1. Use trac-admin initenv to create the database structure
2. Use mysqldump --no-data to dump the database structure into trac.mysql.sql
3. Use TRUNCATE to get rid of your default data, it will be replaced by the import:

   TRUNCATE `attachment` ;
   TRUNCATE `auth_cookie` ;
   TRUNCATE `component` ;
   TRUNCATE `cache` ;
   TRUNCATE `enum` ;
   TRUNCATE `milestone` ;
   TRUNCATE `node_change` ;
   TRUNCATE `permission` ;
   TRUNCATE `report` ;
   TRUNCATE `repository` ;
   TRUNCATE `revision` ;
   TRUNCATE `session` ;
   TRUNCATE `session_attribute` ;
   TRUNCATE `system` ;
   TRUNCATE `ticket` ;
   TRUNCATE `ticket_change` ;
   TRUNCATE `ticket_custom` ;
   TRUNCATE `version` ;
   TRUNCATE `wiki` ;
   

4. Use sqlite .dump to dump the structure + data from sqlite into trac.sqlite.sql, unfortunately there's no option to only dump the data.
5. Remove all the structure ('create table' and 'create index') from trac.sqlite.sql You could use this simple Perl script or the more complete Python script mentioned below:

   $ cat cleansql
   #!/usr/bin/env perl
   
   $_ = join("", <>);
   
   $_ =~ s/^CREATE.*?\);$//smgi;
   
   print $_;
   
   # NEOF
   
   $ ./cleansql trac.sqlite.sql >  trac.sqlite.sql.dataonly
   

6. Concatenate trac.mysql.sql and trac.sqlite.sql.dataonly into trac.sql

   cat trac.mysql.sql trac.sqlite.sql.dataonly > trac.sql  
   

---

You should open the trac.sql file in a text editor of choice and replace all \ with \\ as otherwise, these will be interpreted as escape symbols by MySQL.

---

SQLite uses utf8 as default. If you have your server configured with encoding other than utf8 and you can't change that, you are going to get your data badly encoded. While you may have already set your MySQL database to use utf8 as the default character set, you could still have problems when importing data. As an example for the console client:

mysql trac_db -h host -u user -p --default-character-set=utf8 < trac.sql

An alternative to the cleansql above:

$ cat cleansql.py
#!/usr/bin/env python

import sys
import re

file = sys.stdin.read()
file = re.sub(r'(CREATE (TABLE|INDEX)[^;]*|COMMIT|BEGIN TRANSACTION);', '', file)
file = re.sub(r'INSERT INTO "([^"]+)"', lambda m: 'INSERT INTO `%s`' % m.groups(1), file)
sys.stdout.write(file)

$ ./cleansql.py < trac.sqlite.sql > trac.sqlite.sql.dataonly

---

One caveat is that the reports stored in the report table might not work as expected. You can solve this by:

1. Dropping the report table from my newly migrated Trac MySQL database
2. Dumping the report table from the temporary Trac MySQL database to get the schema in steps 1 and 2 at the top of the page
3. Loading the sql dump back in to my newly migrated Trac MySQL database

This will only restore the default Trac queries. If you had custom queries, you will still need to re-write them if they don't work right on MySQL.

mysql -D tracmysql -e "drop table report"
mysqldump -D temptracdbforschema report > report.sql
mysql -D tracmysql < report.sql

You need to get the full report table from the MySQL database you created for its schema in to your new Trac MySQL database. This also assumes that you did not have any custom queries and were just using the defaults.

---

One 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.

This page contains a summarised procedure: ​http://www.pokesoft.net/blog/?p=473

This is a modified Python cleansql script, which takes in both the MySQL table structure SQL and the SQLite SQL. It will remove the PRAGMA statement and convert CAST(p.value AS int) to CAST(p.value AS signed). It also fixes the backslash escaped quotes.

---

None of the scripts here deal with quoting of ' characters caused by sqlite/mysql differences. Here is a Perl script for SQLite to MySQL migration, which handles quoting very accurately:

print "BEGIN;\n";
print "TRUNCATE `$_`;\n" for (qw(attachment auth_cookie cache component enum milestone node_change permission report
                                 repository revision session session_attribute system ticket ticket_change ticket_custom version wiki));
my ($inq,$del);
sub qut { local $_=shift; ($inq ? (/'/ ? "\\" : ($inq=0,"'")) : "'".(/'/ ? '' : ($inq=1,''))).$_ }
while (<>) {
	$del=!/;/, next if ($del);
	s/^(COMMIT|BEGIN TRANSACTION);//mg;
	$del=1, next if (/^CREATE (TABLE|INDEX)/);
	s/INSERT INTO "([^"]+)"/INSERT INTO `$1`/g;
	s/\\/\\\\/g;
	s/'(.|$)/qut($1)/ge;
	s/(INSERT INTO `milestone` .*),0,NULL/$1,NULL/g;
	print;
}
print "COMMIT;\n"