mco_edge_trans_commit

Commits the changes made within an edge database transaction.

For an overview, see the Edge Client page.

Prototype

    MCO_RET mco_edge_trans_commit(mco_trans_h t);
    

Arguments

Description

Commits all modifications made during the specified transaction, analogous to mco_trans_commit() in the core runtime.

If an error occurs during transaction execution (e.g., within a wrapper API call such as Class_field_put()), the error is recorded internally and will be returned by all subsequent API calls for that transaction, including mco_edge_trans_commit(). In such cases, the transaction is automatically rolled back, and the stored error code is returned to the caller.

After a successful commit, the transaction becomes eligible for transmission to the main eXtremeDB instance via mco_edge_sync() Note that edge data transmission is only initiated when mco_edge_sync() is called, not automatically at the transaction commit time. That provides extra flexibility to edge applications. For example, the application can call the synchronization API in a separate thread, transferring the data in parallel. Or the applications can call _sync() not after every commit, but only when the edge database becomes full.

Return Codes

Files