-
Break up transaction brackets
Ninox offers possibilities to break the transaction context with the instruction do as deferred. Let's assume that an external system is to be informed when an invoice status changes.…
-
Transactions
All triggers on data creation or change, and all scripts within do as transaction or do as server, run within a transaction that either executes fully or does not execute at all if it terminates.…
-
Buttons
Ninox scripts triggered by buttons (or when a formula field is clicked) run in the context of the client and not as a transaction. This means that Ninox executes command by command separately,…
-
Table views
The performance of table views is influenced by three factors: the complexity of the query (filter) the number of rows to be loaded the data loaded per row Ninox calculates views in the following…
-
Best Practices
The following best practices are key recommendations that have proven particularly effective when working with Ninox. They address common pitfalls such as inefficient data access,…
-
Scripting
do as transaction ... end | do as server ... end | do as deferred ... end Ninox executes scripts in a perpetual exchange between the browser or app and the server.…
-
Tips and tricks
Learn how to boost the performance of your databases First, a checklist of common questions and advice:
What are the potential bottlenecks? A look at the process monitor helps identify areas for…