Using Caché Objects - InterSystems Documentation

Set Status = TargetSyncSet.Import(file,lastSync,maxTS,displaymode,errorlog,diag)
where
• file is the file containing the data for import.
• lastSync is the last synchronized transaction number (default from synctime table).
• maxTS is the last transaction number in the SyncSet object.
• displaymode specifies whether or not output appears for the method's actions, where
“d” specifies that output appears and “-d” specifies that it is silent.
• errorlog provides a repository for any error information (and is called by reference
to provide information for the application).
• diag provides more detailed diagnostic information about what is happening when
importing
This method puts data into the target database. It behaves as follows:
a. If the method detects that the object has been modified on both the source and target
databases since the last synchronization, it invokes the
%ResolveConcurrencyConflict callback method; like other callback methods, the
content of %ResolveConcurrencyConflict is user-supplied. (Note that this can
occur if either the two changes both modified a common property or they were to
non-intersecting sets of properties.) If the %ResolveConcurrencyConflict method
is not implemented, then the conflict remains unresolved.
b. If, after the Import method executes, there are unsuccessfully resolved conflicts,
these remain in the SyncSet object as unresolved items. It is the responsibility of the
application programmer to take the appropriate action regarding the remaining conflicts;
this may involve resolution, leaving the items in an unresolved state, etc.
If this process completes, the Import method returns success.
Other Topics
8. Once the first database updates the second database, perform the same process in the
other direction so that the second database can update the first one.
17.3 Other Topics
This section addresses other actions related to object synchronization. These include:
Using Caché Objects 153