Databases

01The primary database

Each server has a primary MariaDB database, created at installation and marked "Primary" in the Databases screen. It is the framework's, and the one read by scripts that go through oxmysql, as most do: their tables live there next to Nova's. It cannot be deleted.

The Nova framework tables are hidden and protected there: the editor does not show them, and no operation can touch them from the site. They change with Nova updates; yours stay yours.

02Extra databases

"New database" creates another one, under the chosen name (lowercase letters, digits and underscores). The "databases used" counter includes the primary database: depending on your plan, there may be no room left for one more. On NOVA INFINITY, an add-on adds some (subscription and invoices).

An extra database stays separate: scripts that go through oxmysql do not read it. It is for keeping data apart, not for installing a script. Deleting it is final: all its data is lost, take a backup first (backups).

03The editor

"Manage" opens a database's editor. On the left, its tables; on the right, two tabs. "Data" browses rows page by page, and lets you add, edit or delete a row. "Structure" shows the columns, and lets you add, edit or delete one. "Create a table" adds a table, with at least one column; a name reserved by the framework is refused.

A row is edited through its primary key: a table without a primary key, or with a binary one, can be read but not edited row by row. Binary, BIT, geometric or generated columns stay read-only, and a very long value is truncated on display. A row referenced by another table can only be deleted after the rows that point to it.

04Importing a .sql file

In the editor, "Import a .sql file" runs an export in the open database. The file is checked in full before it runs: 10 MB and 50,000 statements at most. Procedures and triggers (DELIMITER), views, grants, database switches, and any statement touching a Nova framework table are refused.

Once started, an import that stops on an error leaves the previous statements applied, and the screen says at which statement it stopped. An import that runs over ten minutes stops too. Take a backup right before, split a large export, and import only your scripts' tables (coming from another framework).

05Who can do what

"View databases" lets you list databases and browse their tables: the viewer and the operator have it. "Manage databases" lets you create and delete a database, change a table and import: it is the right of the administrator and the owner (inviting your team). A suspended server keeps its databases, but they can no longer be changed.

A server script placed in resources/[client] uses the same database account as the framework, and can therefore read the whole primary database. Only install scripts whose origin you know.

06Support access

Support never reads your database without your consent. If it needs to for a request, it explains why and asks for access for a limited time. You accept or refuse it in Data access ("Allow", "Refuse"), you can take it back before it ends ("Withdraw access"), and every read is recorded there: table list, table structure, row reads.