On Mon, 2006-04-24 at 11:52 +0200, Christoffer Soop wrote: > Matthew Good skrev: > > In DB version 17 the columns "kind" and "change" in the table > > "node_change" were renamed to "node_type" and "change_type" > > respectively. You will need to change them back so the queries used in > > 0.9.5 will work. > Seems like I am missing another column "sql", as shown by the trace > quoted below. > > Digging through the code I have found that the report table has a definition > > CREATE TABLE report ( > id integer PRIMARY KEY, > author text, > title text, > query text, > description text > ); > > Judging from the source code the "query" column really should be "sql" > instead. > > My first guess was that I have missed a db upgrade script somewhere > along the way but looking through the available scripts (using "grep -i > report") I cannot find something that seems relevant. > > Of course I can change this by creating my own upgrade script but I > don't understand how trac ended up in this state since the tracs checks > the database_version at runtime. (Maybe this is a new feature?) > > Looking through the db_default.py and trac-admin it seems like the there > has never been a column called query... > > Does anybody know what's going on?
Your project was upgraded with a version of Trac from the trunk with patches for MySQL applied. This column was renamed since it conflicted with a keyword in MySQL: http://projects.edgewall.com/trac/attachment/ticket/986/trac-sqlcolfix-r2944.patch It looks like that is the only additional schema change from the MySQL patches. -- Matthew Good <[EMAIL PROTECTED]> _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
