Hor911

Canonize tree branch order (Grace Joins etc)

1

In plan tree view some branched (i.e. Grace Join inputs) are fully equivalent. Currently they are printed in random order, so the same plane can be rendered differently. It complicates...

Because they have little to nothing useful for user Currently ``` │ -> Filter (Predicate: Exist(item.n.n_regionkey)) │ -> InnerJoin (Grace) (Condition: 0,1 = 0,1) │ -> Filter (Predicate: Exist(item.c.c_nationkey) And...

Most important attributes should go first Currently: ``` TableFullScan (ReadColumns: ["n_name","n_nationkey"], ReadRanges: ["n_nationkey (-∞, +∞ )"], Table: tpch10/nation) ``` Proposed: ``` FullScan (Table: "tpch10/nation", Columns: ["n_name","n_nationkey"]) ```

Since they're completely useless

SQL: ``` o.o_orderdate >= Date("1993-12-01") ``` Plan: ``` item.o_orderdate >= "8735" ```

Currently: ``` │ -> Filter (Predicate: Exist(item.c.c_nationkey)) │ -> InnerJoin (Grace) (Condition: 0 = 0) │ -> Filter (Predicate: Exist(item.o.o_custkey)) │ -> InnerJoin (Grace) (Condition: 0 = 0) │ ->...

For large plans it is impossible to match (second) nodes link after is several lines Some kind of vertical lines is needed to pair node and its subnode ``` ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬────────┬────────┐...