Modify

Opened 7 years ago

Closed 6 years ago

#2669 closed defect (fixed)

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

Reported by: mmarques Owned by: 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 (1)

scrumburndownplugin.diff (565 bytes) - added by mmarques 7 years ago.
patch adding a commit

Download all attachments as: .zip

Change History (6)

Changed 7 years ago by mmarques

patch adding a commit

comment:1 Changed 7 years ago by mmarques

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

comment:2 Changed 6 years ago by anonymous

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

comment:3 Changed 6 years ago by mmarques

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

comment:4 Changed 6 years ago by daan

  • Owner changed from sambloomquist to daan

comment:5 Changed 6 years ago by daan

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed The owner will remain daan.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.