Magic xpa Locking (Magic xpa 3.x)

This property is mainly relevant for ISAM databases.

Magic xpa manages its own locking mechanism at the row and table levels without transactions by using the mglock.data file. These locks are referred to as Magic xpa locks and can be enabled by setting the Magic xpa Locking property to Record Lock or Table Lock. Because SQL RDBMS locking is always invoked, there is usually no need for an additional locking mechanism when accessing an SQL database in a physical transaction mode task.

Setting the Magic xpa Locking property to None implies that only the underlying database’s concurrence controls will be in effect.

If the Magic xpa Locking is set to Table or Both, the Magic xpa Runtime tries to open the table infinitely. If the Magic xpa Locking is set to None and the Magic xpa Rutnime fails to open the database table because of locking, then the task is terminated.

Available options: None, Record, Table, Both

Relevant interfaces: This property is not relevant for SQLite or Local databases.