Data Management – Contexts (Magic xpa 3.x)
In contexts, it is not possible to define shared transactions. If the called task opens a transaction, it will open a new transaction. If the transaction mode is:
-
Deferred – a new deferred transaction will begin
-
Nested deferred – a new deferred transaction will begin
-
Within Active – a new transaction will begin according to the Magic xpa defaults
The cache mechanism is per context.
|
Note:
|
There is a possibility that one context will lock another. If this happens, the user will get the message “record is being locked by another user” in which the current user is actually the other user.
|
Memory tables need to be passed explicitly. Memory tables will not be automatically copied. To copy a memory table, use the MTblSet function. If the Mtblset function is used in the Task Prefix of a program or task, the table is currently empty, and the memory table is defined as a data source for this program, the table will immediately be reopened for use (with the new data) and ready for use within the program.
