NJustyBaseDocumentation

user guide

JustyBase documentation

A practical guide to the JustyBase SQL workspace, from the first connection to production-safe data workflows.

Supportedv3.18.6 · verified 2026-08-19

#Work from question to trusted result

JustyBase is a multi-database SQL workspace for VS Code. It combines a parser-backed editor, schema intelligence, operational tools, and a result explorer so the database context stays close to the work.

This portal is the canonical documentation for the VS Code extension and its companion extensions. The reference catalog is generated from the current extension manifests and the database matrix is the place to check dialect boundaries. Pages labelled Desktop only, Read-only, Partial, or Preview describe deliberate product boundaries.

#Six workflows worth starting with

If you need to… Start here
Understand why the editor catches a problem before execution Parser, LSP and SQL Editor
Configure table aliases and virtual JOIN relationships SQL completion guide
Review safety, correctness, performance, and type warnings SQL quality and diagnostics
Explore a large result without losing control of the data boundary Data Grid and Result Exploration
Move data between files and databases Import and export
Find an object or a column across a warehouse Schema Search
Use AI while keeping execution and privacy explicit AI SQL Assistant

#Choose your route

#New to JustyBase

Read Getting started, save a connection, open the Schema Browser, and run the small query from that page. Then use Connections to understand active database context per tab.

#Moving from another SQL client

The product guides cover the workflows that are easy to miss in a feature list: metadata refresh and Schema Refresh Details, result-set persistence, all-rows filtering, staged imports, query history, DDL, and maintenance.

#Extending JustyBase

The developer guide explains the boundaries between contracts, shared SQL/runtime/UI packages, the VS Code extension, and companion extensions. Testing and documentation describes the checks expected when a capability changes.

#Status vocabulary

Supported means the workflow is implemented and covered by the current product surface. Partial means the main path exists but the dialect or platform has a stated limitation. Preview marks a capability that may change. Read-only means the feature intentionally does not write data. Desktop only identifies a VS Code-specific surface. See Statuses and permissions for the full legend.

#Version and evidence

This portal was verified against product version 3.18.6 on 2026-09-26. Generated command, setting, database, AI-tool, and MCP tables are derived from repository sources during the Pages build. The build also publishes machine-readable build metadata with the source commit and generated counts. Narrative pages still require human review when behavior changes.