Wire the Tier-4 tier from ADR-0008 — the first tests that drive the actual built binary in a real pseudo-terminal. tests/e2e_pty.rs spawns the binary under portable-pty at a fixed 100x30, parses output with vt100, and asserts on the rendered screen with tight (3s) fail-fast waits. Serial (one PTY at a time) for predictable timing on the low-parallelism runner; each test gets its own temp --data-dir so it never touches real projects. The four flows mirror ADR-0008's Tier-4 scope: - cold launch -> create table -> graceful quit (Ctrl-C) - create + add column -> quit -> reopen (--resume) -> schema (incl. column) restored - export -> import into a fresh project -> schema + data rebuilt - undo after DROP TABLE, through the confirm modal (y) Table presence is read from the Tables sidebar region (not whole-screen) since the Output panel echoes commands; commands are paced to completion (real-user cadence) — a command sent mid-rebuild can be misread against a stale schema cache (issue #39). Also two NFR perf measurements via the harness (NFR-1 startup, NFR-3 idle RSS) against generous debug-binary bounds for gross-regression detection; the real release figures (median 29 ms / 10 MB) are recorded in the NFR doc. Deps (dev): portable-pty 0.9, vt100 0.16 (both current; expectrl from ADR-0008 dropped — it bundles a conflicting PTY layer). Runs by default in `cargo test`, so the existing Linux CI gate exercises it (advances TT5). PTY-in-container verified (openpty+spawn works under Docker). Full suite: 2519 passed / 0 failed / 1 ignored. clippy + fmt clean. Relates to TT4 / ADR-0008.
rdbms-playground
A cross-platform terminal app for learning relational database concepts — tables, columns, primary and foreign keys, relationships, indexes, queries, and query plans — in a safe sandbox.
It's a teaching tool, not a database administration tool. It meets beginners with guided, keyword-based commands (simple mode) and grows with them to raw SQL (advanced mode), so the same playground works from "what is a primary key?" through to writing real queries and reading their execution plans.
Website & documentation: https://relplay.org
Install
One line (Linux / macOS)
curl -fsSL https://git.lazyeval.net/oli/rdbms-playground/raw/branch/main/scripts/install.sh | sh
Detects your OS and CPU, downloads the matching release binary, verifies
its SHA-256 checksum, and installs it to ~/.local/bin. Set
RDBMS_INSTALL_DIR to install elsewhere, or RDBMS_VERSION=vX.Y.Z to
pin a version. (Prefer to read before you run? The script lives at
scripts/install.sh.)
One line (Windows, PowerShell)
irm https://git.lazyeval.net/oli/rdbms-playground/raw/branch/main/scripts/install.ps1 | iex
Downloads the matching .exe, verifies its checksum, installs to
%LOCALAPPDATA%\Programs\rdbms-playground, and adds it to your user
PATH. Or use a package manager (Scoop / winget) once those land.
With cargo binstall
If you have cargo-binstall
(install it first — it is not part of cargo itself):
cargo binstall rdbms-playground
From source
cargo install rdbms-playground # from crates.io
# or, from a clone:
cargo build --release # binary at target/release/rdbms-playground
Prebuilt binaries
Every release publishes static Linux, standalone Windows, and macOS
binaries (x86_64 and aarch64) with .sha256 checksums on the
releases page.
Windows users can also use the binary directly (package-manager support
is planned).
A quick taste
create table Customers with pk id(serial)
add column Customers: name (text)
add column Customers: email (text)
insert into Customers values ('Ann', 'ann@example.io')
show data Customers
Press F1 while typing for a contextual hint about the command you're
building, or type help for the full command list. Switch to raw SQL
with mode advanced (or prefix a single line with :).
Project status
Approaching its first public release. See the website for current features; installation via package managers (Homebrew, Scoop, winget) is on the roadmap.
License
Dual-licensed under either of
- MIT license (LICENSE-MIT)
- Apache License 2.0 (LICENSE-APACHE)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual-licensed as above, without any additional terms or conditions. See CONTRIBUTING.md.