Trac environment upgrade fails using MySQL

[jluna]

When [re-]creating the TracForge tables, MySQL drops out with:

Incorrect table definition; there can be only one auto column and it must be defined as a key

Anyhow, it's an easy fix. The annoying part is that it leaves the database in a half-updated state. Perhaps upgrade_environment should be wrapped in a generic try-except block to perform a database rollback in the event of an error?

[Paul.Thomson@…]

Replying to jluna:

When [re-]creating the TracForge tables, MySQL drops out with:

Incorrect table definition; there can be only one auto column and it must be defined as a key

Anyhow, it's an easy fix. The annoying part is that it leaves the database in a half-updated state. Perhaps upgrade_environment should be wrapped in a generic try-except block to perform a database rollback in the event of an error?

[anonymous]

I am having the same problem - could you please let me know your fix?

Many thanks,

Paul

[Noah Kantrowitz]

I do not test on MySQL, nor do I plan to, so consider this even more unsupported than normal.

[anonymous]

Yeah, thanks for that. Big help for those of us who choose to use MySQL for various legitimate reasons.

[anonymous]

FIX IS SIMPLE:

--- tracforge/admin/db_default.py.orig  2007-12-27 12:00:17.000000000 -0800
+++ tracforge/admin/db_default.py       2007-12-27 12:00:26.000000000 -0800
@@ -7,7 +7,7 @@
         Column('name'),
         Column('env_path'),
     ],
-    Table('tracforge_project_log', key=('project', 'action'))[
+    Table('tracforge_project_log', key=('project', 'action', 'id'))[
         Column('id', auto_increment=True),
         Column('project'),
         Column('action'),