Execution context

do as database ... end is available for Private Cloud/On-Premises.

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.

A client is the program that is executed on an end device of a network, communicating with a server. Depending on what needs to be done, Ninox executes an instruction directly at the client or at the server.

Description	Transaction type	Web app	Native app
Data management
➡️ Create	Write	Server	Client
➡️ Change	Write	Server	Client
➡️ Delete	Write	Server	Client
➡️ Load views	Read	Server	Client
Scripting
➡️ General (no data change)	Read	Client	Client
➡️ General (at least one data change)	Write	Server	Client
➡️ select	Read	Server	Client
➡️ do as transaction	Read/Write	Server	Client
➡️ do as server	Read/Write	Server	Server
➡️ do as deferred	Read/Write	Server	Server
➡️ do as database	Read/Write	Client	Client
➡️ Trigger after open	Read/Write	Client	Client
➡️ Trigger on new record	Write	Server	Client
➡️ Trigger after update	Write	Server	Client