“For the proper functioning and stability of your databases“
Ninox developper
Jacques_TUR
2 days ago
Reported - view
Good question, I understand your concern better now!
The latest stable version is 3.0.5. That's the one currently available.
Regarding your question about risks to a database:
Ninext does not touch the data or the schema of Ninox. No version of Ninext has ever modified or deleted data in a database.
However, two things can happen and probably explain your question:
The JavaScript that Ninext allows to execute may, depending on how it is used, create unusual behaviors in Ninox. This remains under the control of the developer who writes that code.
A bug in Ninext itself can, in certain specific cases, prevent a Ninox script from executing correctly. This is exactly what happened in version 3.0.4 with some where clauses inside select statements (fixed in 3.0.5). In such cases, the data is not damaged, but the behavior of the database changes — some calculations or automations may stop working as expected, as long as the database is running the buggy version.
What we have put in place since then:
From now on, every new version of Ninext is tested in real conditions on a live database, by several users, before publication. This helps us avoid releasing major bugs. That said, no software is ever fully safe from a defect that might have escaped our tests — if you notice anything unusual, don't hesitate to report it here.
Ninox developper
Jacques_TUR
2 days ago
Reported - view
An important clarification about the schema
When I say that Ninext does not touch the database schema, this should be understood as follows: Ninext never modifies the schema automatically. To ensure a complete separation between Ninext and Ninox, a copy of the schema is even kept in memory on the Ninext side, so that internal processing cannot impact the actual schema.
However, some actions deliberately triggered by the user — such as copy/pasting a field — obviously do modify the schema, since that is their very purpose. In such cases, Ninext relies as much as possible on Ninox's native functions to perform these modifications, rather than acting directly on the schema from its own code. The goal is for every change to go through Ninox's official mechanisms, which ensures the consistency of the database.
