ScrumBurndownPlugin, trac 0.10.4, mysql

what version of mysql are you using ?

i've got the same problem. my version of mysql is 5.0.45-Debian_0+tld0-log

hi there again,

In case if your using the mysql 5.x version, You will need to provide some changes in the burndown.py to upgrade your database properly and with no data loss like milestone table removment. if you run the upgrade command and it fail, you will see that this table was dropped!

on line: 84

"""CREATE TEMP TABLE burndown_old as SELECT * FROM burndown;""",

replace with

"""CREATE TEMPORARY TABLE burndown_old as SELECT * FROM burndown;""",

on line: 103

"""CREATE TEMP TABLE milestone_old AS SELECT * FROM milestone;""",

replace with

"""CREATE TEMPORARY TABLE milestone_old AS SELECT * FROM milestone;""",

and on line: 106

name            TEXT PRIMARY KEY,

replace with:

name            VARCHAR(255) PRIMARY KEY NOT NULL,

and now You may build Your egg file using python setup.py bdist_egg, copy it from dist dir to your plugins dir, place the burndown.* = enable in your trac.ini conf and THEN (and only then), make trac-admin /your/env upgrade

you should see that the upgrade was maded with success - thus, that was in my case.

If you have more this kind issues, report them and try to specify the solution for your base version.

MESSAGE TO BURNDOWN.PY AUTHOR: Take under the consideration optimising the fields types that your script creates.

creating a table like:

"""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
);""",

and setting the type of field to TEXT is not as good solution as You may think. Consider to changing it to something like varchar 255. OR varchar(25) - how much of data will be stored in field "year" - it is quite sure that more than 25 characters will not be kept in that field. Think about the db memory which need to be alocated while performing the operations on those tables.

Optimise your SQL code !

quick info:

you will also need to set auto_increment value on id field in burndown table.

otherwise you wont be able to choose "start milestone" option.

(In [5058]) Release of version 1.9.1 of the Trac Scrum burndown plugin. See http://stuq.nl/weblog/2008-12-25/scrum-burndown-plugin-191-released for more information.

A new version of the Scrum Burndown plugin for Trac is released, bringing compatibility for PostgreSQL, MySQL, Trac 0.11.2.1, and many bug fixes. Upgrading is recommended.

New features The Scrum burndown plugin is currently compatible and tested with Trac 0.10.5, Trac 0.11.1, Trac 0.11.2.1 Python 2.4 and Python 2.5. Additional to the previous SQLite compatibility, support for both PostgreSQL 8.3 and MySQL 5 has been added.

The following issues are fixed:

• Fixes #1462 better control of milestone: a way to ‘reset’ a milestone
• Fixes #1217 database upgrade fails after installing latest scrumburndownplugin
• Fixes #2476 Error: ‘line_graph’ is undefined - stop graph from displaying
• Fixes #1730 couldn’t upgrade
• Fixes #2729 Error while running under PostgreSQL
• Fixes #3102 burndown_job.py fails INSERT NULL id
• Fixes #1909 Overshooting estimate reduces remaining effort while ticket is open
• Fixes #1189 TracBurndown?-01.05.10-py2.4.egg error
• Fixes #1800 No chart when clicking Burndown chart button.
• Fixes #4047 AttributeError?: ‘NoneType?’ object has no attribute ‘getValue’
• Fixes #2224 Changing ticket component causes removal from burndown
• Fixes #2562 Creating a new component breaks the burndown graphic for “All Components”
• Fixes #4222 Install fails on mysql
• Fixes #2218 ScrumBurndownPlugin, trac 0.10.4, mysql