Changes between Version 6 and Version 7 of SqLiteToMySql

Timestamp:

Sep 30, 2007, 6:26:01 AM (17 years ago)

Author:

cyberkni

Comment:

adding notes about the report table

SqLiteToMySql

@@ -50 +50 @@
 sys.stdout.write(file)
 
-$ cat trac.sqlite.sql | ./cleansql.py > trac.sqlite.sql.dataonly
+$ ./cleansql.py < trac.sqlite.sql > trac.sqlite.sql.dataonly
 }}}
+----
+One gotcha for all this is that the reports stored in the report table might not work as expected. I solved this by:
+ 1. Dropping the report table from my newly migrated trac mysql db
+ 2. Dumping the report table from the temporary trac mysql db I created 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 db
 
-this doesn't work
+One catch is that 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 db you created for its schema in to your new mysql trac db. This also assumes that you did not have any custom queries and were just using the defaults.