http://wiki.melissadata.com/index.php?action=history&feed=atom&title=MatchUp_Object%3AIncremental%3ATransaction 2026-06-16T16:07:28Z Revision history for this page on the wiki MediaWiki 1.43.1 http://wiki.melissadata.com/index.php?title=MatchUp_Object:Incremental:Transaction&diff=9436&oldid=prev 2015-07-30T20:31:51Z

<p>Created page with &quot;{{MatchUpObjectIncrementalNav |FunctionsCollapse= }} {{CustomTOC}} These functions enable the Incremental interface to use transactions, processing multiple calls to the [[M...&quot;</p> <p><b>New page</b></p><div>{{MatchUpObjectIncrementalNav<br /> |FunctionsCollapse=<br /> }}<br /> <br /> {{CustomTOC}}<br /> <br /> These functions enable the Incremental interface to use transactions, processing multiple calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function before committing the changes to the key file.<br /> <br /> ==BeginTransaction==<br /> This function tells MatchUp Object to wrap subsequent multiple calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function with a transaction block.<br /> <br /> 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|CommitTransaction]] function is called. The transaction functions are used in the same way that BEGIN, COMMIT and ROLLBACK are used in SQL.<br /> <br /> 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|CommitTransaction]] function. Thus, transaction processing should not be used if multiple threads, processes, users, or machines are accessing the same Incremental database.<br /> <br /> This function returns true when transaction processing is successfully initialized.<br /> <br /> {{ Object Syntax<br /> |Syntax=BooleanValue = mdMU-&gt;BeginTransaction()<br /> |C=BooleanValue = mdMUIncrementalBeginTransaction(mdMU)<br /> |.Net=BooleanValue = mdMU.BeginTransaction<br /> }}<br /> <br /> <br /> ==CommitTransaction==<br /> This function tells MatchUp Object to commit, or add, the previous calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function to the key file since the [[#BeginTransaction|BeginTransaction]] function was called.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> This function returns true when an existing transaction has successfully completed.<br /> <br /> {{ Object Syntax<br /> |Syntax=BooleanValue = mdMU-&gt;CommitTransaction()<br /> |C=BooleanValue = mdMUIncrementalCommitTransaction(mdMU)<br /> |.Net=BooleanValue = mdMU.CommitTransaction<br /> }}<br /> <br /> <br /> ==RollbackTransaction==<br /> This function enables you to roll back or erase the previous calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function from the last call [[#BeginTransaction|BeginTransaction]] function. A boolean value of &#039;&#039;&#039;true&#039;&#039;&#039; is returned if a successful rollback is completed.<br /> <br /> 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.<br /> <br /> 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.<br /> <br /> {{ Object Syntax<br /> |Syntax=BooleanValue = mdMu-&gt;RollbackTransaction()<br /> |C=BooleanValue = mdMUIncrementalRollbackTransaction(muMU)<br /> |.Net=BooleanValue = mdMU.RollbackTransaction<br /> }}<br /> <br /> <br /> [[Category:MatchUp Object]]</div>

Admin