ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Product Release

Database workbench: live query results, SQL EXPLAIN and JavaScript debugging

The database workbench adds auto-refreshing query results, a SQL EXPLAIN action, a JavaScript debugger with a configurable port, an Explorer context menu, and a console split into separate stdout and stderr tabs.

The browser-based database workbench is where an engineer runs queries, inspects schema and debugs server-side code against any of the supported engines. This release sharpens the everyday loop: results stay live, execution plans are one click away, and JavaScript running on the server is now debuggable from the same surface.

Query results and execution plans

  • Auto-refresh. The results panel refreshes on an interval while keeping the current rows visible, so a monitored query updates in place instead of clearing and redrawing.
  • SQL EXPLAIN. An EXPLAIN action sits in the execution flow, returning the engine's plan for a statement without leaving the editor.
  • Steadier toolbar. The results toolbar holds its position across refreshes, removing the jitter a redraw introduced.

Explorer and metadata

  • Right-click context menu. The Explorer tree exposes its actions through a right-click menu on each node.
  • Focus follows the active tab. Selecting a database tab moves the Explorer tree focus to the matching node, so the tree and the open query stay in agreement.
  • Metadata search. The metadata viewer gains search and refresh, so a column or index is found by name rather than by scrolling.

Server-side JavaScript debugging

  • Debug URL builder. The workbench builds the debugger URL for a running script and copies it to the clipboard, so attaching a debugger is a paste rather than a hand-assembled address.
  • Configurable debug port. The JavaScript debug port is configurable, so the debugger attaches on the port the environment allows.
  • Split console. Console output separates into stdout and stderr tabs, so diagnostics read apart from ordinary output.

Each change is scoped to the workbench surface; existing queries, scripts and connections are unaffected, and the new actions appear alongside the tools already in the panel.

See the feature →

← All posts