Maximilian Hoffman

I've collected evidence suggesting 1) we execute a number of remote fetches proportional to the number of branches, 2) for static replicas with 1000 branches on a local remote server,...

this is still broken as of dolt `0.50.8`

repro: ```sql > create table xy (x int primary key, y int); > select x, sum(y) from xy group by x order by avg(y); column "AVG(xy.y)" could not be found...

As of dolt `1.35.9` we error on this: ```sql tmp/main*> create table xy (x int primary key, y int); tmp/main*> insert into xy values (0,0); Query OK, 1 row affected...

Natural joins are just broken generally, and we need to do more work before we would get indexing to work. The main problem is how we handle NATURAL_JOIN projections. Currently,...

Looks like https://github.com/dolthub/go-mysql-server/pull/1907 fixes this. NATURAL and USING joins funnel to the same operator, which is simplified into the equivalent projections+inner/left join.

As of `1.35.9` we've fixed the ambiguity but do not log the warning here.

#benchmark

Test for repro: ```golang { Name: "range query convert int to string zero value", SetUpScript: []string{ `CREATE TABLE t0(c1 VARCHAR(500), PRIMARY KEY(c1)); -- PK is needed to reproduce the issue`,...

Test with the forced lookup and order required to trigger the error path: ```golang { Name: "range query convert int to string zero value", SetUpScript: []string{ `CREATE TABLE t0(c0 VARCHAR(500));`,...