Data Editor

Browse, insert, edit and delete rows in any database you can reach through Next DB, using a fast, paginated grid.

Opening the editor

The editor is where you land after you log in to the Joomla administrator and open Next DB. If you have more than one profile, you first see the Profile Picker.

Step 1 — Select a profile

The Profile Picker shows every published profile assigned to your Joomla account (or to one of your user groups). Super Users see all published profiles and can switch freely between them. Choose a profile to enter the editor with that profile's permissions.

Profiles you use often can be starred to float them to the top of the Favourites section. Recently used profiles appear as one-click chips above the full list.

Step 2 — Select a connection

Once the profile loads, the Connection Selector in the header shows the databases your profile can reach. The Joomla site database always appears as "Joomla site database". Stored connections appear by their configured title.

Whatever you pick is your active session: every action (browse, insert, structure, export, and so on) applies to that profile and connection together. You can switch either one at any time from the header without reloading the page.

Object tree

The left sidebar lists every table and database view your profile can see on the active connection. The list is sorted alphabetically and refreshes whenever you switch connections.

Filter box

A text field at the top of the sidebar narrows the list to names that contain what you type (case-insensitive). Filtering is instant.

Toolbar items

These items appear above the filter box only when your profile grants the matching permission. Each is hidden if you don't have that permission.

Tables vs views

Tables carry a grid icon; views carry an eye icon. Both can be browsed. Views are always read-only in the editor (see Read-only situations below).

Table scope

If your profile is limited to a list of tables on this connection, only those tables appear — others are invisible, not just disabled.

Browse grid

Clicking a table name in the object tree opens the Browse view: a paginated data grid.

Pagination

Only the current page of rows is loaded at a time, and the pager shows the correct number of pages from the total row count.

• Default page size comes from Settings → Editor → Default page size. The page-size picker offers 25, 50, 100 and 200, plus your configured default.
• Maximum: 500 rows per page. A request for more than 500 rows is reduced to 500.

Sorting

Click any column header to sort ascending; click again for descending. Only one sort column is active at a time.

NULL display

Cells that hold a SQL NULL value show an italic grey NULL badge instead of an empty cell, so you can always tell a NULL apart from an empty string at a glance.

Note: All browsing is done safely — your input is validated on the server before any query runs.

Row editor drawer

Clicking a row — or the Add row button in the toolbar — opens the Row editor drawer on the right side of the screen. The drawer handles both adding and editing rows.

Editing the right row

Next DB uses the table's primary key to target the exact row you edit or delete. Tables with no primary key are read-only — a banner explains this, and Add, Edit and Delete are turned off. You can still view the data.

How fields are shown

The drawer shows one field per column, with the column name as the label and a short hint about the column's type below it:

Adding a row

When you save a new row, only real columns of the table are stored. If nothing valid was entered, the save is refused with a clear message.

Editing a row

When you save an edit, the change targets only the specific row you opened, identified by its primary key. A change that would somehow affect every row is refused.

Deleting a row

The delete icon on a grid row opens a confirmation dialog ("Delete this row? This cannot be undone.") before anything happens. Deleting is only available from the grid's row actions, not from inside the drawer, and it always targets the single row by its primary key.

Audit trail

When your active profile records add, edit or delete actions, the change is written to the audit log:

• Add — the new values are recorded.
• Edit — the row is captured before the change and the new values after it.
• Delete — the row is captured before it's removed.

Sensitive columns (password, secret, token, and similar) are masked in these snapshots. See Audit policy for retention and visibility settings.

Read-only situations

Several things can make a table, or one action on it, unavailable. In every case the table is still browsable unless Browse itself is denied.

Next DB hides controls you don't have permission to use, and the server enforces every permission independently — so you can't get around a limit by working around the screen.

Engine notes

The editor works the same across all three hardened engines, with a few small differences:

See also

• Profiles and ACL
• SQL Console
• Structure Editor
• Export & Import