Database Field
The following database fields are available:
|
Database Field Name |
Equivalent Parameter Type |
|---|---|
|
Int32_A |
Boolean or Numeric32Bit |
|
Int32_B |
Boolean or Numeric32Bit |
|
Int32_C |
Boolean or Numeric32Bit |
|
Int32_D |
Boolean or Numeric32Bit |
|
Int64_A |
Numeric64Bit |
|
Int64_B |
Numeric64Bit |
|
Int64_C |
Numeric64Bit |
|
Int64_D |
Numeric64Bit |
|
Double_A |
NumericFloat |
|
Double_B |
NumericFloat |
|
Time_A |
DateTime |
|
Time_B |
DateTime |
|
String_A |
String |
|
String_B |
String |
|
String_C |
String |
|
String_D |
String |
The division into database fields is optional, because the entire action (with parameters) is written to the EventData field (also known as BLOB).
If important parameters are written in the fields, this has the advantage that you can use e.g. filters in the G-View event list.
If a parameter needs to be written in a database field or more database fields, then the parameter needs the attribute dbfield with an indication of one or more flags.
<parameters>
<parameter name="Value" type="Numeric64Bit" dbfield="Int64_A"/>
<!-- OR -->
<parameter name="Value" type="EventType" dbfield=" Int64_A|String_A"/>
</parameters>Otherwise you don’t need to add the attribute dbfield.