Maximilian Hoffman

The union error is fixed, now blocked on an aliasing issue: ``` column "COUNT(t1.id)" could not be found in any table in scope ``` The error resolves if I manually...

The last 3 are all correct afaik, the first query with the error is definitely a bug. @JCOR11599 this could be a good one for you.

The only thing that is going to make this faster is putting filters into the memo, rewriting pushdown, implementing table statistics, and then using filter selectivity + statistics in costing.

```sql sbt> explain SELECT c_discount, c_last, c_credit, w_tax FROM customer1, warehouse1 WHERE w_id = 1 AND c_w_id = w_id AND c_d_id = 2 AND c_id = 2327; +---------------------------------------------------------------------------------------------+ | plan...

Apologies for the delay, some details on how to implement `STORED`/`VIRTUAL` below if materializing `VIRTUAL` generated columns as NULL fields in value tuples. I suspect read/write round tripping will have...

```sql > create table xy (x int primary key, y int); > delete a from xy a join xy b on a.x = b.x; table doesn't support DELETE FROM ```

I think this was a feature request, not a bug. Someone wanted to do multiquery without a server and they had to manually scan a string for semi-colon separated queries.

Fine w me, the checks in the Dolt repo have worked well enough on their own.

@KOLANICH this partial solution might be of interest to you: https://github.com/dolthub/doltcli It's a bit easier for me to carve out a full-featured and dependency-less subsection of doltpy for engineers than...

It's an internal distinction we make between using dolt's CLI and SQL interfaces. In the future we'd like to use a raw SQL session with pymysql or another connector to...