| 173 | A possible approach (until someone comes up with a better one?!) is to use the sqlite engine to export the tickets and changes, generate a script, and then insert the records into the second trac installation. E.g.: |
| 174 | |
| 175 | :: |
| 176 | |
| 177 | [root@xgbemf6002 root]# sqlite <path/to/trac_project/db/trac.db> |
| 178 | SQLite version 2.8.15 |
| 179 | Enter ".help" for instructions |
| 180 | sqlite> select * from ticket; |
| 181 | 1|1092797666|1094723786|component1|normal|normal|Martin|someone@somewhere.com|||||reopened||test|testing| |
| 182 | sqlite> select * from ticket_change; |
| 183 | 1|1092798124|leigh|comment||Testing notification |
| 184 | 1|1092798319|leigh|owner|somebody|Leigh |
| 185 | ... |
| 186 | ... |
| 187 | |
| 188 | |
| 189 | It should be possible to take this output , and produce a script that would insert records into the ticket and ticket_change tables in the new trac installation. |
| 190 | |
| 191 | As provided below, the database schema can be found here_. |
| 192 | |
| 193 | .. _here: http://projects.edgewall.com/trac/file/trunk/trac/db_default.py?rev=latest |
| 194 | |
| 195 | |