Modify

Opened 11 years ago

Closed 11 years ago

#701 closed defect (fixed)

Burndown job fails if there is no data

Reported by: tomt@… Owned by: Sam Bloomquist
Priority: normal Component: ScrumBurndownPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.9

Description

If there is no data in the burndown table then the burndown_job.py will fail.

The actual problem is caused by the following line being called prior to insert a record into the table. It's erroneous to print this out before inserting anyway, as get_last_id will return the value of the previously inserted record, not the one just (or just about to be) inserted:

print 'burndown: %i, %s, %s, %s, %i' % (db.get_last_id(cursor, 'burndown'), 
  comp[0], mile[0], today, hours) 

In the attached file I've moved the print statement to after the insert. There's also a wee problem when calling rows = cursor.fetchall() in the same method. If rows is nil the for loop following will fail.

Attachments (1)

burndown_job.py (3.1 KB) - added by tomt@… 11 years ago.
Burndown job

Download all attachments as: .zip

Change History (2)

Changed 11 years ago by tomt@…

Attachment: burndown_job.py added

Burndown job

comment:1 Changed 11 years ago by Sam Bloomquist

Resolution: fixed
Status: newclosed

Removed the offending print statement as part another fix.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Sam Bloomquist.
The resolution will be deleted.

Add Comment


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

 
Note: See TracTickets for help on using tickets.