data_log_grp
- Last UpdatedNov 20, 2024
- 2 minute read
The data_log_grp table defines a group of related data items to be sampled together.
The obsolete field is used to specify that this data log group is no longer usable, but that it is not deleted to preserve the context of existing data log data collected for it.
|
Field |
Datatype |
PK |
Nulls? |
Description |
|---|---|---|---|---|
|
grp_desc |
string254 |
N |
N |
Group description, must be unique |
|
max_value |
int32 |
N |
N |
Historically used to indicate which data_log_n table to use. In upgrades, this might be 16 or 48. All new data log groups set this to 64. The data_log_16 view returns data_log records that are linked to max_value = 16. The data_log_48 view returns data_log records that are linked to max_value = 48. |
|
trigger_type |
int32 |
N |
N |
Enumeration of trigger type: 0 = manual 1 = tag 2 = job change 3 = shift change 4 = step change 5 = lot change Note: Currently, only the manual trigger type (0) is supported by the system. |
|
trigger_detail |
string1000 |
N |
Y |
XML formatted detail for the trigger – depends on the trigger type. Note: Currently, the trigger_detail field is not used by the system. |
|
obsolete |
logical |
N |
N |
Is this data log group obsolete? Default = No. |
|
spare1 |
string1000 |
N |
Y |
Use defined by language term 4279 |
|
spare2 |
string1000 |
N |
Y |
Use defined by language term 4280 |
|
spare3 |
string1000 |
N |
Y |
Use defined by language term 4281 |
|
spare4 |
string1000 |
N |
Y |
Use defined by language term 4282 |
|
last_edit_comment |
string254 |
N |
Y |
Reserved for internal use to indicate why this record was changed |
|
last_edit_by |
string40 |
N |
Y |
Who last changed this record |
|
last_edit_at |
tdatetime |
N |
N |
When this record was last changed |
|
mod_id |
timestamp |
N |
N |
A binary number that increments each time the row is modified. |
|
grp_id |
ID 1 |
Y |
N |
Identify data log group |
grp_desc is UK.