Package io.objectbox.sync
Class SyncFlags
java.lang.Object
io.objectbox.sync.SyncFlags
Flags to adjust sync behavior like additional logging.
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final intIf the client gets in a state that does not allow any further synchronization, this flag instructs Sync to keep local data nevertheless.static final intLogs sync filter variables used for each client, e.g.static final intEnable (rather extensive) logging on how IDs are mapped (local <-> global)static final intEnables debug logging of TX log processing.static final intWhen set, remove operations will include the full object data in the TX log (REMOVE_OBJECT command).static final intSkips invalid (put object) operations in the TX log instead of failing. -
Method Summary
-
Field Details
-
DebugLogIdMapping
public static final int DebugLogIdMappingEnable (rather extensive) logging on how IDs are mapped (local <-> global)- See Also:
-
ClientKeepDataOnSyncError
public static final int ClientKeepDataOnSyncErrorIf the client gets in a state that does not allow any further synchronization, this flag instructs Sync to keep local data nevertheless. While this preserves data, you need to resolve the situation manually. For example, you could backup the data and start with a fresh database. Note that the default behavior (this flag is not set) is to wipe existing data from all sync-enabled types and sync from scratch from the server. Client-only: setting this flag for Sync server has no effect.- See Also:
-
DebugLogFilterVariables
public static final int DebugLogFilterVariablesLogs sync filter variables used for each client, e.g. values provided by JWT or the client's login message. Server-only: setting this flag for Sync client has no effect.- See Also:
-
RemoveWithObjectData
public static final int RemoveWithObjectDataWhen set, remove operations will include the full object data in the TX log (REMOVE_OBJECT command). This allows sync filters to filter out remove operations based on the object content. Without this flag, remove operations only contain the object ID and cannot be filtered. Note: this increases the size of TX logs for remove operations.- See Also:
-
DebugLogTxLogs
public static final int DebugLogTxLogsEnables debug logging of TX log processing. For now, this only has an effect on SyncClients (Sync Server has extensive debug logs already).- See Also:
-
SkipInvalidTxOps
public static final int SkipInvalidTxOpsSkips invalid (put object) operations in the TX log instead of failing.- See Also:
-