Viewing & Editing Data
Once your schema is ready, you'll spend most of your time looking at actual rows — debugging, fixing typos, exploring what your app is producing. DYPAI gives you two ways to do that: a spreadsheet-style view for normal edits, and a full SQL editor for anything more.
Browsing rows
Click any table in the Database tab to see its rows.
The row view works like a spreadsheet:
- Click a cell to edit. Press
Enterto save,Escto cancel. - Click a column header to sort.
- Right-click a row for delete, duplicate, and copy options.
- Scroll down to load more — rows load in pages of 100.
Changes save immediately. There's no "unsaved changes" state to worry about.
Filtering and searching
Use the filter panel above the grid to narrow things down:
- Stack multiple filters — they're combined with
AND - Pick from common operators per column type (
=,!=,>,<,contains,in) - Filters are URL-encoded so you can share a filtered view with a teammate
For full-text search, use the SQL editor — the filter panel is for exact matches and ranges.
The SQL editor
For queries the visual editor can't express, there's a full SQL console. Open it from the SQL button above any table or at the top of the Database tab.
Things you can do here:
- Run any
SELECT,INSERT,UPDATE,DELETEonpublic - Run
CREATE TABLE,ALTER TABLE,CREATE INDEXfor schema changes - Inspect
systemschemas (read-only) — useful for checking users, roles, endpoint metadata
Recent queries are saved per project so you can re-run them later.
Destructive queries run without confirmation
DROP TABLE, TRUNCATE, and unfiltered DELETE / UPDATE execute the moment you hit run. There's no "are you sure?" prompt. Use LIMIT 1 or wrap in a transaction if you're unsure.
Exporting data
From the row view, click Export in the toolbar:
- CSV — one row per record, headers included. Good for spreadsheets.
- JSON — array of objects. Good for feeding into scripts or other apps.
Exports respect the current filter — so you can filter to "tasks done this week" and export just those.
Importing data
Click Import and pick a CSV file. The import dialog lets you map CSV columns to table columns and pick what to do on conflicts (skip, update, or fail).
Imports run in a single transaction — either all rows succeed or none do.
What NOT to edit manually
Some schemas are read-only for good reasons. Don't try to modify them directly:
| Schema | What's in it | Why hands-off |
|---|---|---|
system | Users, roles, endpoints, agent chats | Managed by the auth engine. Manual edits break it. Use the SDK or the Auth tab. |
auth | Sessions, tokens | Managed automatically. |
storage | File metadata | Synced from the file system. Don't edit rows directly. |
You can read from them freely (SELECT * FROM system.users), just don't write.