Running Transactional Queries in the Lakebase SQL Editor
Who this is for:
Architecture / Concept Overview: Running Transactional Queries in the Lakebase SQL Editor
The Lakebase SQL Editor connects to your Lakebase engine through the same PostgreSQL wire protocol used by external clients, but with an integrated UI that provides syntax highlighting, auto-completion, and result visualization.
%%{init: {"theme":"base","themeVariables":{"background":"#0B0E14","primaryTextColor":"#E0E6ED","lineColor":"#5D6470","darkMode":true,"primaryColor":"#2E4A4A","secondaryColor":"#374151","secondaryTextColor":"#E0E6ED","tertiaryColor":"#111827","tertiaryTextColor":"#E0E6ED","edgeLabelBackground":"#1f2937"}}}%%
flowchart LR
classDef source fill:#3F4B59,stroke:#9CA3AF,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef ingestion fill:#5A4B36,stroke:#C9A86B,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef processing fill:#535072,stroke:#8E82B4,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef storage fill:#2E4A4A,stroke:#5FAFA8,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef serving fill:#3D5550,stroke:#6BB7AA,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef governance fill:#5A3F52,stroke:#C28BB0,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
A[Developer] -->|Browser| B[Lakebase SQL Editor]
B -->|Wire Protocol| C[Lakebase Engine]
C -->|Read/Write| D[Lakebase Storage]
B -->|Schema Browser| E[Table Metadata]
C -->|Sync| F[Delta Lake / Unity Catalog]
A:::source
B:::serving
C:::processing
D:::storage
E:::ingestion
F:::governance
*The SQL Editor provides an in-browser interface that communicates with the Lakebase engine using the standard PostgreSQL protocol.*
%%{init: {"theme":"base","themeVariables":{"background":"#0B0E14","primaryTextColor":"#E0E6ED","lineColor":"#5D6470","darkMode":true,"primaryColor":"#2E4A4A","secondaryColor":"#374151","secondaryTextColor":"#E0E6ED","tertiaryColor":"#111827","tertiaryTextColor":"#E0E6ED","edgeLabelBackground":"#1f2937"}}}%%
graph TD
classDef source fill:#3F4B59,stroke:#9CA3AF,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef ingestion fill:#5A4B36,stroke:#C9A86B,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef processing fill:#535072,stroke:#8E82B4,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef storage fill:#2E4A4A,stroke:#5FAFA8,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef serving fill:#3D5550,stroke:#6BB7AA,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
classDef governance fill:#5A3F52,stroke:#C28BB0,stroke-width:2px,rx:8,ry:8,color:#E0E6ED
A[SQL Editor Features] --> B[Query Execution]
A --> C[Schema Explorer]
A --> D[Transaction Control]
A --> E[Result Export]
B --> F[Single Statement]
B --> G[Multi-Statement Transactions]
D --> H[BEGIN / COMMIT / ROLLBACK]
D --> I[Auto-Commit Mode]
A:::processing
B:::serving
C:::source
D:::governance
E:::ingestion
F:::storage
G:::storage
H:::governance
I:::governance
*The SQL Editor supports single and multi-statement execution, schema browsing, transaction control, and result export.*
Key Terms
Prerequisites and Setup
- A Lakebase project with at least one database containing tables
- Access to the Databricks workspace UI
- Sufficient Lakebase permissions (
SELECT,INSERT,UPDATE,DELETE) on the target tables
Step-by-Step Implementation
Configuration Reference
| Setting | Description | Default |
|---|---|---|
| Auto-commit mode | Automatically commit each statement | Enabled |
| Result row limit | Maximum rows displayed in results | 1000 |
| Statement timeout | Maximum execution time per statement | Workspace default |
| Editor theme | Syntax highlighting theme | Matches workspace theme |
| Branch context | The database branch queries execute against | main |
| Result format | Display format for result sets | Table view |