Write transactions

When you change data within an action, this is referred to as a write transaction.

Examples of write transactions

• The input or modification of data

• Single statements of a script that change data, e.g., via a button

• All statements within a do as transaction or do as server block, if at least one statement can potentially change data

Trigger on create and trigger after update are executed within the write transaction through whose instructions they were triggered.

Only one write transaction can be executed at a time. All other write transactions have to wait for their turn.

However, this does not pose a concern, since write transactions are usually executed within a few milliseconds, so that multiple users can access Ninox at the same time without any restrictions.

Special cases

It may happen that Ninox appears to be slow or unresponsive. This may be due to a transaction that takes a bit more time to execute your instructions and therefore blocks subsequent transactions in the queue.

Possible causes of delay in the execution of write transactions

• Queries of external services, e.g., API calls via http()

• Extensive data evaluations in combination with select statements