Tables surface

The daily database surface. Browse rows, edit cells, drill through foreign keys, run bulk operations, mask sensitive columns, edit JSON as a tree.

#Browsing

Action How

Open a table

Sidebar → table name. URL is permalink-safe (

/db//tables/.).Filter Header bar + filter. Builds a typed where clause matching the engine's filter API.
Sort Click a column header. Multi-sort with shift-click.
Find on page ⌘F — searches loaded rows only, doesn't re-query.
FK drilldown Cell with an FK link → arrow icon → opens the parent row in a side panel.
#Editing
TXT
6 lines
1Single cell    : double-click → inline editor. Saves on blur or Enter.
2Multiple cells : shift-click range → bulk edit modal.
3Insert row     : header "+ row". Required columns highlighted; FK fields
4                 get a typeahead from the parent table.
5Delete rows    : select checkboxes → toolbar "delete". Confirmation modal
6                 with the SQL preview before commit.
Every edit emits the same compiled query the engine would — it goes through the adapter, the plugin chain, and writes to the audit log just like an application query.
#Bulk operations
Operation Use when
**Bulk update** Set the same value across the selection. SQL preview shown before commit.
**Bulk delete** Same shape — confirmation modal with row count.
**Export** Selection or full filtered query → CSV / JSONL / SQL INSERT statements.
**Import** CSV → pasted row append. Type-checks against the column types.
#Sensitive masking
Columns marked sensitive in the schema render as **** by default. Click the eye icon to reveal — the action writes a row to the audit log. Studio respects the same field-level sensitive: true the engine reads from the schema.
TS
9 lines
1// Mark a field sensitive via the meta channel — Studio reads this flag and masks the column.
2const User = defineModel((m) => ({
3  name: 'User', table: 'users',
4  fields: {
5    ...m.id(),
6    email: m.string().meta({ sensitive: true }),         // → masked in Studio by default
7    passwordHash: m.string().meta({ sensitive: true }),
8  },
9}));
Heads up
Reveal events end up in the audit table even when the viewer has read access. If your compliance posture says "every access to PII is logged," this is the trail you point at.
#Special editors
Type Editor
json / jsonb Tree editor — expand keys, edit leaves, validate against an optional inline schema.
bytea Hex / base64 toggle. Image preview if the bytes start with a known image header.
Array columns Per-element editor with type-checked add/remove.
Range types Two-input editor with the inclusive/exclusive bracket toggles.
← previous · StudioWorkspace levelCross-database — connections, activity, search.next · Studio →SQL playgroundMulti-tab editor, plan history, watch, charts.