In Ninox, all actions are performed as transactions. In doing so, a sequence of database operations is summarized in a transaction.

We distinguish 2 types of transactions in Ninox:

• Read

• Write

Ninox executes transactions either in the client or on server.

To find specific records in a table using a filter, Ninox searches the table for records that match the filter. During this process Ninox only "reads" the table in order to display the records that correspond to the filter.

Ninox always searches the table that was up-to-date at the moment of the query. Changes to data—for example by co-workers—that were added during the current query are not included.

Ninox can process many read transactions simultaneously without delaying or blocking other 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

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

Ninox executes transactions either in the client or on server.

On one hand, which transaction is executed on server or in the client depends on its type (read or write). On the other hand, it also depends on whether the transaction was triggered in the web app or the native app.