The SLG table holds the entries for modifications to master file tables. The entries hold the control information.
The data of the modified entry is stored in a separate Savedata structure in the directory 'log' of the 'data' partition using the StreamSaveInSubdir routines.
The Savedata structure holds the data as afterimage.
The SLG-table holds records for each modification of master file tables as AIJ. The record contents is stored separately as a blob with savedata with the INR of the SLG-record as identification.
These entries are created by then central log functions in the Systemmodule prefixed by SLG.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Log Entry | Text | 8 | 1 | Edit | Yes | Public | ||
| LOGTYP | Table ID of Record to be Logged | Text | 6 | 1 | Edit | Yes | Public | ||
| LOGINR | INR of Record to be Logged | Text | 8 | 1 | Edit | Yes | Public | ||
| LOGFRM | ID of Transaction Creating log entry | Text | 8 | 1 | Edit | Yes | Public | ||
| FCT | Function | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| DATTIM | Timestamp of Modification | Datetime | 15 | 0 | Unknown | Yes | Public | ||
| USR | User ID | Text | 8 | 1 | Edit | Yes | Public | ||
| VER | Version Counter of Record | Text | 4 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| SLG_INR | INR | Unique |
| SLG_LOG | LOGTYP, LOGINR |
/
INR
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter SLG. The field INR is used to maintain links from other tables into this table. The INR is additionally used as file name in the directory structure 'data/log' to hold the savedata structure of the log entry.
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
This field holds the table ID of the master file table.
This field holds the table ID of the master file table.
This field holds the INR of the logged entry. The associated table is identified by the field LOGTYP.
This field holds the unique ID of the logged entry. The associated table is identified by the Table ID field.
This field identifies the type of the logged function. Because of the possibility of recovering a 'Delete', the functions 'Insert' and 'Delete' might be executed more than once in the historic sequence of modifications. When 'Undeleting' an entry, this is stored as an 'Insert'.
This field identifies the logged function type. Because of the possibility of recovering a 'Delete', the functions 'Insert' and 'Delete' can be executed more than once in the historic sequence of modifications. When 'Undeleting' an entry, this is stored as an 'Insert'.
| Code | Text |
|---|---|
| U | Updated |
| D | Deleted |
| I | Inserted |
Date and time when the modification was stored.
Date and time when the modification was saved.
User ID of the user issuing the modification.
User ID of the user issuing the modification.
All versions of a master file entry are sequentially numbered in the field VER that is kept in the master file entry. The initial entry starts with the version number zero. Versions with numerical numbers greater than 10.000 will be stored as alphanumeirc values.
The versionnumber in table SLG refers to the entry specified by table ID and INR. This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.
Transaction code under which this log entry was created.