We’ve been experimenting with a more reproducible and narrative SQL workflow inside VS Code, and ended up building a SQL Notebook feature into our extension. It mixes SQL queries, Markdown, and results, and it stores everything in a single .exabook file.
The motivation was mostly practical: teams were writing SQL in one tool, explaining it in another, and sharing screenshots elsewhere. Nothing was reproducible, versionable, or reviewable. So we merged those ideas into one workflow that fits naturally inside VS Code.
Would love feedback, especially on:
- the notebook format
- whether the UX feels natural or awkward
- limitations we might not be seeing where this fits (or doesn’t fit) in a typical SQL workflow
one-random-geek•1d ago
https://github.com/exasol-labs/exasol-vscode
The motivation was mostly practical: teams were writing SQL in one tool, explaining it in another, and sharing screenshots elsewhere. Nothing was reproducible, versionable, or reviewable. So we merged those ideas into one workflow that fits naturally inside VS Code.
Would love feedback, especially on:
- the notebook format - whether the UX feels natural or awkward - limitations we might not be seeing where this fits (or doesn’t fit) in a typical SQL workflow