Creating a synchronization error log table for an application
It is highly recommended that a synchronization error log table is created as part of the database schema of a decentralized system. The log table allows application developers to store information about the application-level errors that might occur during synchronization.
If the error requires manual resolution, the error log serves as a source of the information that is required to correct the error. For instance, if an update conflict occurs, the log can contain information about which row was in conflict and what was done to the conflicted row by the transaction. The following example shows an error log table:
CREATE TABLE ERRLOG (ID CHAR(20) NOT NULL, LOG_TITLE CHAR(80) NOT NULL, LOG_DESCRIPTION VARCHAR NOT NULL, UPDATETIME DATETIME NOT NULL, PRIMARY KEY (ID));
The ID is a generated, globally unique key of the log entry.
The LOG_TITLE and LOG_DESCRIPTION columns contain the information about the error, such as an update conflict.
The UPDATETIME column contains the timestamp of the last update operation of the error log row.