Show query plans in the Linux SQL editor
維護者通常 1 天內回覆
@J2TeamNNL 已經在處理了。
開始於 2026年10月31日。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
研究方向
Start with linux/crates/core/src/statement/statement_builder.rs and the macOS reference features/explain-visualization.mdx; the issue also points to linux/ROADMAP.md. Trace how statements and results are built in the Linux app, then compare each engine’s required plan format. Done means Explain renders a PostgreSQL join as a tree with row estimates and works across the listed engines.
由索引模型根據 Issue 內容生成。
描述
Problem
The Linux app has no way to show a query plan. The user can type EXPLAIN in the editor and read the plan as rows of text, but nothing draws it, and each engine has its own format: text or JSON on PostgreSQL and MySQL, XML on SQL Server, a list of steps on SQLite. The only EXPLAIN in the code is a unit test (linux/crates/core/src/statement/statement_builder.rs:166).
It is not on the roadmap: neither the backlog nor the Ideas list (linux/ROADMAP.md, Backlog, Ideas) mentions it. The macOS app draws plans (features/explain-visualization.mdx).
Proposed solution
- Explain in the editor, for the statement at the cursor or the selection, with a shortcut.
- Each engine runs its own form:
EXPLAIN (FORMAT JSON)on PostgreSQL,EXPLAIN FORMAT=JSONon MySQL and MariaDB,SET SHOWPLAN_XML ONon SQL Server,EXPLAINon ClickHouse, andEXPLAIN QUERY PLANon SQLite. - The plan shows as a tree of nodes in a results entry, built from GTK list widgets, with each node's estimated rows and cost where the engine gives them, and the costliest node marked.
- Explain Analyze, where the engine has it, runs the statement, so it asks first. On a statement that writes, it is refused on a read-only connection and otherwise runs inside a transaction that is rolled back.
- The raw plan text stays one click away, for copying.
Done means: on PostgreSQL, Explain on a join shows a tree with row estimates, and the same action works on the other engines with their own plan formats.
Alternatives considered
Run EXPLAIN by hand in the editor and read the rows.
Platform
Linux
Related database type
N/A / General
- 主要語言
- Swift
- 星號
- 6.2k
- 分支
- 412
- 平均合併
- 3 小時 56 分鐘
- 30 天內合併 PR
- 669
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
TableProApp/TablePro 的其他 Issue
-
Linux: Remember Password fails silently when there is no default keyring可能已有人在做 @datlechin 今天認領。 未關閉bug platform-linux
難度 2/5 1-3 小時 新手友好度 75/100
TableProApp/TablePro#4098 ·
維護者通常 1 天內回覆
-
bug platform-linux
難度 2/5 1-3 小時 新手友好度 35/100
TableProApp/TablePro#4101 ·
維護者通常 1 天內回覆
-
bug platform-linux
難度 4/5 3-5 天 新手友好度 48/100
TableProApp/TablePro#4099 · 3 則留言 ·
維護者通常 1 天內回覆
-
enhancement platform-macos
難度 5/5 一週以上 新手友好度 25/100
TableProApp/TablePro#4071 ·
維護者通常 1 天內回覆
-
enhancement platform-macos
難度 3/5 1-2 天 新手友好度 66/100
TableProApp/TablePro#4070 ·
維護者通常 1 天內回覆
查看 TableProApp/TablePro 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 83/100
OneBusAway/vehicle-positions#260 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 85/100
eliasstravik/herdr-projects#789 · 1 則留言 ·
-
follow-up needs-triage S3: minor
難度 1/5 1-3 小時 新手友好度 85/100
manaflow-ai/cmux#38032 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 67/100
arkavo-org/ArkavoKit#70 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 70/100
vorssaint/vorssaint-utils#3933 · 1 則留言 ·
維護者通常 2 天內回覆