Trac db upgrade and reports

[dpeterson]

Last night we moved a few Trac repositories from Trac 0.84 to the latest downloadable build of Trac 0.9 (I think its beta 1?). We ran the Trac db upgrade script and noticed the following in our reports:

1) The phrase 't.type AS type' was inserted in all the reports but was frequently inserted such that the report query didn't have SQL syntax. It looks like its simply being inserted in front of the word 'severity' with no concept of the fact that your report might have been written like 't.severity AS severity'. I say this because that phrase ends up like 't.severity AS t.type AS type AS severity' which breaks the report.

2) We have written most of our reports to use the m.time (milestone due date) field. None of these references were upgraded to be m.due. Since you guys know there were schema changes, it would be nice if you could detect these sorts of things and change them automatically so that we don't have to go edit track down the new schema and modify all the reports by hand (we've got at least 20 reports in 4 different instances of Trac.)

[dpeterson]

Correction: the line ends up being

t.severity AS t.type AS type, t.severity,

[Christopher Lenz]

It'd probably be best to simply not upgrade the reports. We'd need to have a proper SQL parser to do it correctly.

The problem that reports cannot be easily upgraded in an automatic fashion when schema changes happen are exactly the reason why I'd like to see them be completely replaced by the new query module. Sigh.

[Christian Boos]

wontfix, for the reasons mentioned in comment:2.