Commit e868d5cc authored by Leigh B. Stoller's avatar Leigh B. Stoller

Add new DB fields for dealing with pause/continue of event time. See

commit logs in tbsetup for more info.
parent 14d9673d
......@@ -631,6 +631,9 @@ CREATE TABLE experiment_template_instances (
uid varchar(8) NOT NULL default '',
start_time datetime default NULL,
stop_time datetime default NULL,
pause_time datetime default NULL,
continue_time datetime default NULL,
runtime int(10) unsigned default 0,
runidx int(10) unsigned default NULL,
template_tag varchar(64) default NULL,
export_time datetime default NULL,
......
......@@ -3724,3 +3724,17 @@ last_net_act,last_cpu_act,last_ext_act);
alter table experiments add dpdbpassword varchar(64) default NULL;
4.93: Add pause_time field to template instance to track when user
stops time. Since this is strictly for the purposes of setting
the timestamps on "record" events, its very simple. In other
words, this ain't gonna support time travel!
**** Skip this stuff below if you just did 4.41 above.
alter table experiment_template_instances add \
pause_time datetime default NULL after stop_time;
alter table experiment_template_instances add \
continue_time datetime default NULL after stop_time;
alter table experiment_template_instances add \
runtime int(10) unsigned default 0 after continue_time;
......@@ -309,6 +309,9 @@ CREATE TABLE experiment_template_instances (
-- A little bit of duplication ...
start_time datetime default NULL,
stop_time datetime default NULL,
pause_time datetime default NULL,
continue_time datetime default NULL,
runtime int(10) unsigned default 0,
-- The current experiment that is running (see below). One at a time!
runidx int(10) unsigned default NULL,
-- The tag for the template at the time of instantiation.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment