#18 Alter auto clock-off script to properly end labordtl

closed
Adam Ellis
5
2004-01-18
2004-01-14
Adam Ellis
No

There is a nasty bug in the original auto clock-off
scripts that can cause labordtl records to get out of
sync with the laborhed records. The original scripts
look at both tables independantly and end any active
records that have been logged onto for more than a
user-defined number of hours. This causes a condition
where laborhed will end after, say, 15 hours but the
last labordtl record will stay open until it has been
open for 15 hours. Alter the process to drive only off
laborhed.

Discussion

  • Adam Ellis
    Adam Ellis
    2004-01-18

    • status: open --> closed
     
  • Adam Ellis
    Adam Ellis
    2004-01-18

    Logged In: YES
    user_id=643906

    See auto_clock_off.py