System table ASYS_AUDIT

The system table ASYS_AUDIT contains the following columns:

Column	Description
ACOLUMNAME	Name of the logged column.
ALIAS	Name of the alias within which a change has taken place.
ATABLENAME	Name of the table within which a change has taken place.
ATIMESTAMP	Date of logging when the transaction was performed.
AUSER	The user who initiated the action that led to the audit.
DATASETID	ID of the record where individual columns have changed.
DATASETNEWVALUE_BLOB	Logged new value of a BLOB column.
DATASETNEWVALUE_CLOB	Logged new value of a CLOB column.
DATASETNEWVALUE_STRING	Logged new value of any other column except CLOB and BLOB.
LOGTIME	Date of logging when the element was written to the AUDIT table.
LOGTYPE	Log type, refers to what is logged (NEWVALUE_STRING, _CLOB, _BLOB).
LOGWRITERUID	UID of the log writers.
SQLACTION	Logged Action.

SQLACTION

The SQLACTION column specifies which action was logged. This is either specified by the system, or can also be entered manually in the system table, for example to perform certain actions for data synchronization.

Insert (System)

All data of the columns caused by an "insert" are logged here.

Update (System)

All data that has been changed during an update is logged here.

Delete (System)

Here the ID of the record which was deleted is logged in the DATASETID column.

Unknown Statement (System)

If a statement is written to the database without using ADITO’s own methods db.inserts, db.insertData, db.updates, db.updateData, db.deletes or db.deleteData (e.g. via db.cell (“update org set orgname = 'something'”), or similar commands), the statement will be logged and entered as SQLACTION X.

Process (User)

This SQLACTION is entered manually into the ASYS_AUDIT table. Herewith a JDito process can be specified, which matches certain processes via the restrictions of the ASYS_AUDIT logging.

Change (User)

This SQLACTION is also entered manually in the table. Via Change all records can be synchronized, which fulfill a certain condition, independently of whether with these records a SQLACTION I, U or D is present. About the column LOGTYPE can be returned by entering the values as they are from util.AUDIT_CONDITION_JDITO and util.AUDIT_CONDITION_PLAIN.

Transaction (User)

Similar to C, except that here no data can be deleted or synchronized, but only transferred.

V (V-Power Transaction)

The SQLACTION V corresponds to the transaction, only not all entries in the ASYS_AUDIT are executed with the same LOGTIME in one transaction, but an intermediate commit is executed after a certain time or a certain amount of data has elapsed. The entire audit processes are not considered in the SQLACTION V - not only is no entry made in the ASYS_AUDIT here, the other audit actions are not performed either. Thus the SQLACTION V is very fast.

• All records that exist on the master but not yet on the slave are inserted.

• All data sets, which are present on both sides, are updated at the slave. The values of the records covered by the ID are the current records at the time of synchronization.

• Data records, which are no longer present in the master, are marked at the slave like a delete - that is as if they had been deleted at the master and had been entered as SQLACTION D in the sync table.

Also the V-Transaction is done by a manual entry in the system table ASYS_AUDIT.