Workspace

Query lab

Name: Nexoxa Bridge
Author: Nexoxa

SQL editor, MongoDB shell, and Redis command lab.

The story

These pages use illustrative scenarios to walk through real workbench panels. Sidebar labels, Bridge paths, and connection schemes match the app; characters and timelines are examples for learning.

Incidents live in Query lab — EXPLAIN plans, diagnostic SELECTs, Mongo aggregations, Redis GET bursts — whatever the engine speaks.

Riley keeps Query lab docked beside the grid: write SQL with highlighting, run, inspect plans, tweak, run again. MongoDB shell and Redis command mode share the same keyboard muscle memory.

Schema-aware hints where metadata exists; plain execution where it does not. No ANSI soup in terminal buffers.

Bridge path: /sql

Step 1

SQL with EXPLAIN

Slow endpoint — Riley runs EXPLAIN ANALYZE, sees seq scan on orders, adds index advice to PR.
Results grid exports clean for Slack.

SQL editor, MongoDB shell, and Redis command lab. Path /sql. Syntax highlighting, multi-statement, EXPLAIN for Postgres/MySQL family.

Step 2

MongoDB shell and Redis commands

Same tab switches dialect with connection — aggregation on Mongo, HGETALL on Redis during cross-store bug hunt.
Formatted output beats redis-cli copy-paste.

Engine-specific execution panels. History and copy-friendly results.

Step 3

From Copilot to lab

Copilot suggests a fix query — Riley opens it in Query lab, edits one JOIN, runs against staging first.
Suggested SQL is a draft, not a black box.

Tools → Copilot integration sends SQL to lab. Saved connection context preserved.

This panel appears in the Nexoxa Bridge left sidebar after you connect with the matching connection URL. See the connection docs above for postgresql://, ssh://, sftp://, s3://, or smtp:// examples.

Related connections

Database connection URLs