The admin-only audit trail of executed queries
A searchable history of statements, outcomes and error detail, readable by admins only, and on this engine it also records what the agent was permitted to run.
9 posts
The reference engine — pooled connections, full catalog introspection, visual EXPLAIN, ER diagrams, live health and agent mode. Where it stops: Nothing held back — every capability in the product ships here, including agent mode.
A searchable history of statements, outcomes and error detail, readable by admins only, and on this engine it also records what the agent was permitted to run.
Host-heuristic SSL turns encryption on without verifying the certificate, and two sslmode values are declined by name rather than guessed at.
A tour of the health surface organised by what is missing and why, because a panel that reads Not measured is the only version an operator can act on.
Two EXPLAIN forms with different consequences: the editor emits the executing one, and the agent path emits the planning one only.
The schema tree renders before relationships arrive, and every introspection CTE is materialized on purpose: a 122-table read measured about 295 seconds before the change and about 2.6 seconds after.
Automatic LIMIT injection applies to unbounded SELECT and CTE-SELECT statements only, and there is one statement shape it deliberately leaves alone.
The container-to-container case is the one that breaks: when Studio is itself a container, localhost is its own loopback and the service name is the fix.
Containment is the database itself - a read-only transaction, exactly one statement on the extended protocol, then ROLLBACK and DISCARD ALL.
Agent AUTO mode refuses a superuser connection outright, so the deployment task is a login holding CONNECT, USAGE and SELECT and nothing else.
We use cookies to analyse site traffic and improve your experience. See our Privacy Policy for details.