trac-admin's upgrade --no-backup doesn't create the scrum table

[Martín Marqués]

I installed the TracBurndown (ScrumBurndownPlugin) plugin and when I try to do an upgrade the PostgreSQL database I get an error:

Trac var/trac/> upgrade --no-backup Attempting to create the burndown table Command failed: transacción abortada, las órdenes serán ignoradas hasta el fin de bloque de transacción

In the PostgreSQL logs I find this:

LOG: sentencia: BEGIN; SET TRANSACTION ISOLATION LEVEL READ COMMITTED LOG: sentencia: SELECT value FROM system WHERE name='database_version' LOG: sentencia: SELECT week FROM burndown LIMIT 1 ERROR: no existe la relación «burndown» SENTENCIA: SELECT week FROM burndown LIMIT 1 LOG: sentencia: ABORT LOG: sentencia: BEGIN; SET TRANSACTION ISOLATION LEVEL READ COMMITTED LOG: sentencia: SELECT value FROM system WHERE name='database_version' LOG: sentencia: SELECT week FROM burndown LIMIT 1 ERROR: no existe la relación «burndown» SENTENCIA: SELECT week FROM burndown LIMIT 1 LOG: sentencia: SELECT MAX(version) FROM wiki WHERE name like 'TimingAndEstimationPluginUserManual' ERROR: transacción abortada, las órdenes serán ignoradas hasta el fin de bloque de transacción SENTENCIA: SELECT MAX(version) FROM wiki WHERE name like 'TimingAndEstimationPluginUserManual' LOG: sentencia: ABORT LOG: sentencia: BEGIN; SET TRANSACTION ISOLATION LEVEL READ COMMITTED LOG: sentencia: SELECT * FROM burndown LIMIT 1 ERROR: no existe la relación «burndown» SENTENCIA: SELECT * FROM burndown LIMIT 1 LOG: sentencia: CREATE TABLE burndown ( id integer PRIMARY KEY NOT NULL, component_name text NOT NULL, milestone_name text NOT NULL, date text, week text, year text, hours_remaining integer NOT NULL) ERROR: transacción abortada, las órdenes serán ignoradas hasta el fin de bloque de transacción SENTENCIA: CREATE TABLE burndown ( id integer PRIMARY KEY NOT NULL, component_name text NOT NULL, milestone_name text NOT NULL, date text, week text, year text, hours_remaining integer NOT NULL) LOG: sentencia: ABORT

[Martín Marqués]

patch adding a commit

[Martín Marqués]

Just got a patch up which solved the issue. I don't know if it's fancy, but it worked.

The idea is that if you fail at query "SELECT * FROM burndown LIMIT 1" you have to start a new transaction before starting to execute new queries, else the new queries will be rollback as well. the db.commit() just does that: commits the failed query, so a rollback is executes, and starts a new transaction.

See file ​scrumburndownplugin.diff

[anonymous]

Do you plan to intigrate the patch in the trunk? I ran in to the same problem, patch helped.

[Martín Marqués]

The patch works, but I'm not the maintainer of this plugin.

[daan]

This is solved in the most recent release: ​http://stuq.nl/weblog/2008-11-04/scrum-burndown-plugin-19-released