Virtualized results grid over streaming ResultSet
- Dominant language
- Go
- Stars
- 218
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Own work item — the single biggest chunk of the port (bubbles/table is far weaker than tview.Table). Lazy cell production, batched row streaming from the driver, "rows X-Y of ~N, elapsed" status. Adds the streaming/paged fetch half of ResultSet deferred from v1.0.
**Acceptance (parity gate):** 100k-row result scrolls smoothly; benchmarked rows/sec + peak RSS (/usr/bin/time -l) + idle CPU ~0 recorded in the repo; no full materialization on unbounded queries.
Contributor guide
Research direction
Start by locating the existing ResultSet and table implementation referenced by the issue, including the current tview.Table integration and driver row-fetch path. Benchmark the resulting 100k-row scroll with /usr/bin/time -l and record rows/sec, peak RSS, and idle CPU; done means smooth scrolling without full materialization for unbounded queries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, database, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100