Transactions (Magic xpa 3.x)
Rich Client programs use Deferred transactions. It is not possible to use Physical transactions, because the DBMS is on the server.
In a Deferred transaction, Magic xpa saves up the changes made to the data, then commits them when the transaction ends. If the transaction is rolled back, then the retained transaction information is discarded. This behavior in Rich Client is the same as that in Online programs.
However, there are some differences in the way transactions are handled in Rich Client. In this section we'll look at the similarities and differences:
Transaction Begin
Transaction Mode
Comparison of Online and Rich Client Transaction Modes
The transaction for local data sources behaves as a physical transaction. All the tasks that include a local data source will be on the same transaction. (This is planned to be changed in future versions.)
Commit of the local data is done according to the task that opened the transaction. If a transaction is also opened in sibling tasks, then the data of these tasks will also be committed. (This is planned to be changed in future versions.)
Rolling back a task that has a local data source will roll back:
