Re: design question: storing history

2009-12-14 Thread Shawn Milochik
It sounds like, for auditing purposes, there should be a model for storing each "hours worked" entry. Also, the hours estimated should not be reduced in the database -- there should be a method of your model which returns the remaining hours by subtracting the sum of the worked hours from the e

design question: storing history

2009-12-14 Thread tom
Hi, I have a Model which tracks tasks for a project. This model should have - hours estimated - hours worked on it. Everytime someone updates one of those fields, the hours worked should be increased and should also be stored to be used for time reporting. e.g. hours worked: 12.21.09 2 hours, 1