Skip to content
Manybases
esc

Search pages and sections. Try a tool name, an error code, a route.

↑↓ navigate↵ openesc close
  1. Dashboard
  2. Screens
  3. SQL editor
Docs

Dashboard · Screens

SQL editor

Run one statement against the project's database, and read the history.

The editor runs with your account key, so it bypasses the access presets — you see and change everything. Your app's users never get here. The grammar is deliberately narrow (one statement, no OR, no joins, no aggregates) and is described in SQL.

  • Run (or ⌘⏎ / Ctrl⏎) executes. The result shows the rows and the duration; "No rows matched" means the query ran fine and came back empty. A warning from the API — a table created without a preset, say — is shown under the result.
  • The platform columns (id, owner_id, space_id, created_at, updated_at) cannot be dropped, renamed or written by hand: the whole access matrix is built on them. Neither can the _mb_* tables be reached. Everything else is yours.
  • A statement that destroys data — DROP TABLE, a DELETE or UPDATE that does not name its target with id = …, a dropped or renamed column — asks for a confirmation: "This statement destroys data", with the server's summary. The confirmation only covers this exact statement, and expires in 5 minutes.

History#

The last 50 statements of the project — yours and your agent's — with their status, row count and duration. "Reuse" puts one back in the editor. Results are never kept; the statement text is, with whatever literals it carried.