Maximilian Hoffman

This PR moves us towards arbitrary recursive CTEs clause support. https://github.com/dolthub/go-mysql-server/pull/1226

@snipesjr thank you for the report! I would appreciate any additional debugging context. For example, if the queries are returning incorrect results, sharing how the results are different than expected,...

@snipesjr Just to clarify, query plans or the modified query strings might be easier to share than full result sets. If you set `--trace debug`, the server should log query...

Thank you for the additional details @snipesjr ! Made it much easier to figure out what's going on here. I think the temporary workaround is to use `ORDER BY provider_count`:...

Looks like we are selecting 501 random rows from the left join. We can manually disable parallelism (`SINGLE_THREAD_FEATURE_FLAG dolt sql`), which will give deterministic results, but I presume you want...

@snipesjr I think this one should fix the `sql_select_limit` issue, available in the next release: https://github.com/dolthub/go-mysql-server/pull/1276 Let us know if you run into any more trouble.

The `sql_select_limit` fix should be included in the most recent release here https://github.com/dolthub/dolt/releases/tag/v0.41.6.

`dolt_skip_replication_errors` could be default true?

Some additional notes: 1) We panic trying to import the dump, with a `Found dangling references to HashSet` error logged. The script imports successfully with `SET AUTOCOMMIT = 1;` 2)...

Small status update, I've identified the issue and am making progress in this PR https://github.com/dolthub/go-mysql-server/pull/1247. If I move `ki.interessengruppe_id in (o.interessengruppe_id, o.interessengruppe2_id, o.interessengruppe3_id)` into the where filter (sorting out conjunctions...