Ticket #2669 (closed defect: fixed)

Opened 9 months ago

Last modified 1 month ago

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

Reported by: Martín Marqués <martin@marquesminen.com.ar> Assigned to: daan
Priority: high Component: ScrumBurndownPlugin
Severity: blocker Keywords: upgrade PostgreSQL error
Cc: Trac Release: 0.10

Description

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

Attachments

scrumburndownplugin.diff (0.6 kB) - added by Martín Marqués <martin@marquesminen.com.ar> on 03/06/08 09:55:14.
patch adding a commit

Change History

03/06/08 09:55:14 changed by Martín Marqués <martin@marquesminen.com.ar>

  • attachment scrumburndownplugin.diff added.

patch adding a commit

03/06/08 10:02:44 changed by Martín Marqués <martin@marquesminen.com.ar>

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

10/02/08 03:43:21 changed by anonymous

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

10/02/08 08:27:13 changed by mmarques

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

10/17/08 03:41:14 changed by daan

  • owner changed from sambloomquist to daan.

11/04/08 15:44:12 changed by daan

  • status changed from new to closed.
  • resolution set to fixed.

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


Add/Change #2669 (trac-admin's upgrade --no-backup doesn't create the scrum table)




Change Properties
Action