On Fri, Sep 21, 2012 at 9:55 AM, Steffen Hoffmann <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 20.09.2012 19:07, JackOfAll wrote: > > In 1.0, there is support for multiple repositories, meaning an added > > column for the repository ID in the revision table. I'm migrating from > > 0.10, where there was only support for one repository. I'm migrating to > > 1.0 and don't have a column in the 0.10 database for repo ID. What > > should I set the repo ID column for the migration? > > A default value should be assigned to it on upgrade. This is a standard > procedure and should be dealt with by the db upgrade scripts that come > with your Trac copy. Make a working backup and just run > trac-admin <env> upgrade > afterwards, and you should be fine. > > Note, that you'll likely have to adjust the post-commit hook, that has > changed between 0.11 and 0.12, so take a look at the wiki documentation > to make that work like expected again. > > Steffen Hoffmann > I'm also migrating to MySQL from SQLite. When I try to load the SQL from the SQLite dump, the import fails because there are only 4 parameters in the INSERT statements into the 'revisions' table, when the schema shows that there are 5 parameters and then the import does not continue. Again, any help with the repos column in the MySQL database for Trac with multiple repositories? Rob -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
