You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(explain): visual query plan (Plan | Text) for PostgreSQL, MySQL, SQLite #1164
Explain shows the plan as lines of text in the result grid (QUERY PLAN column, generic_sql_workspace.dart:590). Finding the expensive node in a nested plan means reading indentation.
Scope
Plan formats: PostgreSQL EXPLAIN (FORMAT JSON) (and ANALYZE, BUFFERS behind an explicit Explain analyze action with the destructive-query rules, since it executes the query), MySQL EXPLAIN FORMAT=JSON / EXPLAIN ANALYZE (8.0.18+), SQLite EXPLAIN QUERY PLAN (id, parent, detail already form a tree).
Plan view: a tree (top-down) of nodes with operation, relation, rows (estimated / actual), cost / time; node colour by share of total cost; the most expensive path highlighted. Click a node: details panel with all fields.
Text view kept (today's lines), switch Plan | Text.
Acceptance
PostgreSQL, MySQL, SQLite: a join of 3 tables renders as a tree with the right parent / child structure.
Activity
feat(explain): show the plan as a tree, with Plan | Text (#1164)
fix(explain): MySQL tables keep their own cost; unreadable plan text …
Merge pull request #1227 from QueryaHub/feat/1164-visual-plan
test(explain): tap the plan tree row, not the name repeated in the pa…
Merge pull request #1230 from QueryaHub/feat/1164-plan-node-details
Merge pull request #1249 from QueryaHub/test/1165-1164-1162-debt
ZhuchkaTriplesix commentedon Oct 9, 2026
Closed by #1249: recorded plans for PostgreSQL, MySQL and SQLite, with tree, cost and highlight tests.