Documentation Index
Fetch the complete documentation index at: https://docs.tablepro.app/llms.txt
Use this file to discover all available pages before exploring further.
Last updated: 2026-05-14
What this is
A snapshot of 292 issues from the TablePlus public tracker, cross-referenced against the TablePro feature inventory on main. The set includes both open and closed TablePlus issues. A closed TablePlus issue does not mean TablePro has solved it: it may be a bug that still affects TablePro, a feature TablePlus shipped that TablePro has not, or a request TablePlus declined that users still want. Closed issues are kept only when they still map to a TablePro gap or bug class. The goal is to see, at a glance, which heavily-requested asks TablePro already covers, which are partial, and which are gaps worth prioritizing.
This is internal tracking, not a marketing comparison.
Methodology
- Fetch all issues (open and closed) from
TablePlus/TablePlus, ranked by reactions and by comments. The helper script tags each entry with its state (open or closed) and closed_at.
- Merge the reactions list and the comments list, deduplicated by issue number.
- Categorize each issue into one of: database driver, data grid, editor, SSH and tunneling, import and export, UI / UX, connection form, sync, AI and MCP, security, plugin system, platform, other.
- Mark status against TablePro:
ALREADY_DONE, PARTIAL, MISSING, or OUT_OF_SCOPE. Status comes from the tablepro-feature-inventory.md snapshot taken 2026-05-14, then re-verified against the live main source rather than the inventory snapshot alone. The re-check moved 25 issues to a more accurate status.
- Drop closed issues that map cleanly to
ALREADY_DONE: those describe asks TablePro already covers and add no signal. Keep every open issue, and keep closed issues that are MISSING or PARTIAL, carry the bug label, or have no clear fix in TablePro.
- Compute a priority score:
reactions + (comments * 0.5) plus +20 if the issue carries the bug label.
After the merge and the closed-issue filter, 292 issues remain: 142 open and 150 closed.
Headline numbers
| Status | Count |
|---|
| Already done | 23 |
| Partial | 27 |
| Missing | 240 |
| Out of scope | 2 |
| Total | 292 |
| State | Count |
|---|
| Open | 142 |
| Closed (still relevant) | 150 |
| Total | 292 |
| Category | Count |
|---|
| Database drivers | 139 |
| Data grid | 24 |
| Editor | 8 |
| SSH and tunneling | 15 |
| Import and export | 28 |
| UI / UX | 16 |
| Connection form | 1 |
| Sync and persistence | 3 |
| AI and MCP | 5 |
| Security | 2 |
| Plugin system | 1 |
| Platform | 4 |
| Other | 46 |
How the docs are organized
- Top requests: top 50 issues globally with TablePro status and open/closed state.
- By category: same data grouped by area.
- Gap analysis: Missing items with score >= 30, with priority and implementation hints.
- Quick wins: Missing or Partial items with score >= 20 that look small in scope.
How to use this
When picking up new feature work, check gap-analysis and quick-wins first. P0/P1 gaps map to the next milestone; quick wins are good first issues for contributors.
When triaging bug reports, look up the issue number in top-requests or by-category to see if TablePlus has the same problem at scale (and whether it carries a bug label upstream). A closed TablePlus bug is still worth a regression check in TablePro.
Refresh process
This snapshot is regenerated manually.
1. Fetch the latest issue data. Run the helper script. It writes two JSON files (default output dir: /tmp, override with the first arg). The script fetches issues with state=all, so both open and closed issues are included.
scripts/fetch-tableplus-issues.sh
# or: scripts/fetch-tableplus-issues.sh ./build/competitive-tracking
gh (authenticated) and jq.
2. Re-audit the TablePro feature inventory. Walk Plugins/, Core/, Views/, and docs/ to mark each feature SHIPPED, PARTIAL, or NOT_SHIPPED. The previous snapshot lives in this commit history under the docs-writer team transcript.
3. Merge, re-categorize, and re-score. Merge the two JSON files by issue number. Drop closed issues that map cleanly to ALREADY_DONE. For each remaining issue, assign a category, mark TablePro status (ALREADY_DONE, PARTIAL, MISSING, OUT_OF_SCOPE), and compute the score: reactions + comments * 0.5, plus +20 if the issue carries the bug label.
4. Rewrite the four data pages (top-requests, by-category, gap-analysis, quick-wins) and bump the Last updated date plus the headline tables on this page.