MatchUp Object:Incremental:Transaction

← MatchUp Object Reference

These functions enable the Incremental interface to use transactions, processing multiple calls to the AddRecord function before committing the changes to the key file.

BeginTransaction

This function tells MatchUp Object to wrap subsequent multiple calls to the AddRecord function with a transaction block.

This will greatly speed up processing when adding large numbers of records in the Incremental processor because Records will not be physically written to the Incremental database until the CommitTransaction function is called. The transaction functions are used in the same way that BEGIN, COMMIT and ROLLBACK are used in SQL.

Even though the keys have not been permanently added, Records will still be matched properly. However, other running processes that may be matching against the same database WILL NOT see these new records until after a call to the CommitTransaction function. Thus, transaction processing should not be used if multiple threads, processes, users, or machines are accessing the same Incremental database.

This function returns true when transaction processing is successfully initialized.

Syntax	BooleanValue = mdMU->BeginTransaction()
C	BooleanValue = mdMUIncrementalBeginTransaction(mdMU)
.Net	BooleanValue = mdMU.BeginTransaction

CommitTransaction

This function tells MatchUp Object to commit, or add, the previous calls to the AddRecord function to the key file since the BeginTransaction function was called.

This will greatly speed up processing when adding large numbers of records in the Incremental processor because Records will not be physically written to the Incremental database until this function is called. The transaction functions are used in the same way that BEGIN, COMMIT and ROLLBACK are used in SQL.

Even though the keys have not been permanently added, Records will still be matched properly. However, other running processes that may be matching against the same database WILL NOT see these new records until after the call to this function. Thus, transaction processing should not be used if multiple threads, processes, users, or machines are accessing the same Incremental database.

This function returns true when an existing transaction has successfully completed.

Syntax	BooleanValue = mdMU->CommitTransaction()
C	BooleanValue = mdMUIncrementalCommitTransaction(mdMU)
.Net	BooleanValue = mdMU.CommitTransaction

RollbackTransaction

This function enables you to roll back or erase the previous calls to the AddRecord function from the last call BeginTransaction function. A boolean value of true is returned if a successful rollback is completed.

Even though this function will ensure that the keys have not been permanently added, Records will still be matched properly. Therefore, other running processes that may be matching against the same database will not see these new records. Thus, transaction processing SHOULD NOT be used if multiple threads/processes/ users/machines are accessing the same Incremental database.

This function may also be used when an error is raised with an input or master database, prompting you to gracefully rollback the key file to the point before the current problematic data was processed.

Syntax	BooleanValue = mdMu->RollbackTransaction()
C	BooleanValue = mdMUIncrementalRollbackTransaction(muMU)
.Net	BooleanValue = mdMU.RollbackTransaction