MiG InfoCom MiG Calendar DBConnect Guide - Manual (Page 19)

MiG InfoCom AB
maximum of X milliseconds, or you can showdown the queue after it
has reached size 0.
View the DataSynchronizer JavaDoc for details on how to use
this class.
Queue Action Coalescing
This is an advanced and unique feature of DBConnect. If two
database actions will counter each other out, for instance if the
summary is set in two actions after each other, they can be combined
into one database action. Another example is two poll actions that are
in sequence without delay between them can for instance be merged
into one.
The database coalescing can be set in currently three modes:
DataSynchronizer.COALESCE_NONE - means that there will
be no coalescing.
DataSynchronizer.COALESCE_ADJACENT - means that two
data action will be coalesced only if they are next to each other in the
queue.
DataSynchronizer.COALESCE_REORDER - means that two
data actions will be coalesced so that the data action earlier in the
queue will be removed if a later addition will counter that action out,
even if there are other actions between them. This will in effect
sometimes reorder data actions and they might not end up in the
same order at the backing store as they where produced. Normally
this is not a problem though.
You set the coalescing mode on the DataSynchronizer, for instance
the
ActivityDataSynchronizer .
COALESCE_ADJACENT is the default mode.
Pausing and Resuming the Database Queue/synchronizer
The DataSynchronizer (and thus the
ActivitySynchronizer and CategorySynchronizer)
has a setPaused(boolean) method. It can be used to pause
the data queue as soon as the current data action (if any) is
processed. When the synchronizer is resumed the pending data
actions will continue.
Note that the data queue will still be added to even if the
synchronizer (which owns the queue) is paused. If AutoWrite
is true there will be create/update actions added when
activities and/or categories are changed and if the
DBConnect Guide Page 19 / 25