Tim Sehn

We don't use these systems but we'd happily take a contribution here.

I think we want to do the exact same thing as Git in this circumstance. Yes. Bad idea. But we need to match what the reference implementation does :-)

Then once I restart stats collection I get this: ``` media_wiki/main> call dolt_stats_restart(); +----------------------------------------------+ | message | +----------------------------------------------+ | restarted stats collection: refs/statistics/ | +----------------------------------------------+ 1 row in set (0.00...

I suspect this is irrelevant with the new version of stats.

We have some known issues around prepared statements. We have a PR open to fix them. https://github.com/dolthub/doltgresql/pull/1406 We'll add this bug to the list.

Note, when stats were generated using `call dolt_stats_restart()` the query I was trying to change the plan for that used these three tables started to execute fast. Here's the query:...

A quick once over of the This change has broken four existing bats tests. ```sh not ok 954 import-create-tables: try to table import with nonexistent --pk arg # (in test...

I think this is fine as an isolated change. I would make new PRs for additional checks.

Like you want to be able to push to a remote from Dolt that has an S3 compatible API? And you want that supported in the remote syntax? Can you...

> @timsehn Any update on this? We support S3, filesystem, GCS, and a custom remote server called `remotesrv`. We don't have much demand for more supported remote types. https://docs.dolthub.com/sql-reference/version-control/remotes