Burndown job fails if there is no data

[tomt@…]

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.

[tomt@…]

Burndown job

[Sam Bloomquist]

Removed the offending print statement as part another fix.