User Story #82 (new)
Opened 18 years ago
Last modified 18 years ago
Review available information in Event table. — at Version 3
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | major | Milestone: | 3.0-M3 |
| Component: | Model | Keywords: | iteration5 |
| Cc: | Story Points: | n.a. | |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
Currently the Event type consists of :
- status
- time
- type (enum)
Though the user information is available on the rows that the EventLogs point to, that information is mutable. Each Event should carry Experimenter and Group information and possible other types as well.
Change History (3)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from 3.0-M2 to 3.0-M3
comment:2 Changed 18 years ago by jmoore
- Keywords iteration5 added
comment:3 Changed 18 years ago by jmoore
- Description modified (diff)
From a 2.21 OME db:
Table "public.module_executions"
Column | Type | Modifiers
---------------------+-----------------------------+------------------------------------------------------------
module_execution_id | integer | not null default nextval('module_execution_seq'::regclass)
status | character varying(16) |
r_time | double precision |
iterator_tag | character varying(128) |
dependence | character(1) | not null
timestamp | timestamp without time zone | default now()
x_time | double precision |
image_id | integer |
w_time | double precision |
experimenter_id | integer | not null
virtual_mex | boolean | not null default false
module_id | integer |
dataset_id | integer |
input_tag | text |
error_message | text |
group_id | integer |
new_feature_tag | character varying(128) |
t_time | double precision |
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Will get to it during the security milestone.