GNOME Bugzilla – Bug 417961
Temp table of repetitive events
Last modified: 2007-03-14 16:59:34 UTC
IT will be nice to have a temp table for recording long events (long repetitive jumps or intervallic runs). Then, if the software crashes or if there's any other problem, chronojump should be able to recuperate that event until was last recorded. This events cannot be in normal jumpReactive or runInterval tables with a -1 id, because this can crash with other parts of the software. It will be easy to create two special new tables for this: -tempJumpReactive -tempRunInterval both with the same characteristics than jumpReactive and runInterval but they will contain only 0 or 1 events. And every new event will have the value '1' as uniqueID. in jump, on the first 10 times it will be created the table, and then updated every 10. In inteval run, it will be created at first subrun, and updated every new subrun. When event finish ok, the event on that row will be deleted. On chronojump start (before loading any session), it will check if this event exist, and if exists it will try to recover, and alert the user.
80% done: -need check: (counting & deleteTemp after threads have done) -need: do stuff on start if a temp table is found The tempTables contain more than one event (there's no update, there are Inserts) All the sqlite tempTable events are delete when event is ok