Skip to content

The front door: a database on arrival, and a badge that tells the truth - #36

Merged
YheChen merged 1 commit into
masterfrom
front-door
Aug 5, 2026
Merged

The front door: a database on arrival, and a badge that tells the truth#36
YheChen merged 1 commit into
masterfrom
front-door

Conversation

@YheChen

@YheChen YheChen commented Aug 5, 2026

Copy link
Copy Markdown
Owner

Two things a first-time visitor saw, both accurate and both useless.

The explorer opened empty

Eight panels reading "No database open". True, and not a demo: every panel
needs a database, and somebody arriving from a link has no reason to know that
+ New is the way in.

It now creates one and fills it — two tables, forty users with a NULL age every
seventh row, sixty orders, an index on a non-key column, and ANALYZE. At
256-byte pages that is 48 pages, so:

  • the disk map has something to show, and the heap chain is visible growing
  • the B+ tree view has a real tree with a real height
  • the planner has two access paths to choose between, which is the whole of the
    Execution workspace
  • there are NULLs in it, because three-valued logic is the thing about SQL that
    surprises people most and a demo without any cannot show it

Once, and only when the workspace is genuinely empty. Somebody who deletes the
sample meant to delete it. The seed SQL is in the demo catalogue, so
test_demo_sql.py runs every statement of it against the real engine.

The badge had two states where the engine has three

Between "the transport is up" and "the first /health has answered" nothing is
wrong, and painting that red made the app look broken to its own author for two
minutes
: the WASM build shows a full UI reading disconnected for the tail of
a twenty-second boot. It now says starting, in amber, until the engine answers.

Also

MIT, which this repository should have had from its first commit. The repo
description and fifteen topics are set too — both were empty.

make ci green. 1,715 Python tests, 160 frontend.

Screenshots for the README come next, taken from the deployed build so they show
exactly what a visitor sees.

🤖 Generated with Claude Code

Two things a first-time visitor saw, both accurate and both useless.

The explorer opened on eight panels reading "No database open". That is
true and it is not a demo: every panel needs a database, and somebody
arriving from a link has no reason to know that `+ New` is the way in.
It now creates one and fills it: two tables, forty users with a NULL age
every seventh row, sixty orders, an index on a non-key column, and
ANALYZE. At 256-byte pages that is 48 pages, so the disk map has
something to show, the heap chain is visible, and the B+ tree view has a
real tree with a real height.

Once, and only when the workspace is genuinely empty. Somebody who
deletes the sample meant to delete it.

The connection badge had two states where the engine has three. Between
"transport is up" and "the first /health has answered" nothing is wrong,
and painting that red made the app look broken to its own author for two
minutes: the WASM build shows a full UI reading "disconnected" for the
tail of a twenty-second boot. It says "starting", in amber, until the
engine actually answers.

Also MIT, which the repository should have had from the first commit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
chen-db Ready Ready Preview Aug 5, 2026 7:39pm

@YheChen
YheChen merged commit c3cc6ef into master Aug 5, 2026
6 checks passed
@YheChen
YheChen deleted the front-door branch August 5, 2026 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant