Tim Sehn
Tim Sehn
Probably first step here is to do read-only support for most of these variables and then do a pass on editing them actually changes the behavior of the running server.
Some history compression (though not the form mentioned is this issue) can be achieved with rebase coming soon. Follow along in #3467 .
Interesting idea. I'm not sure how we would implement it but let us discuss internally. There's two things possible: 1. Detecting running servers. Look at open ports and probe whether...
That's another option, we could stick the list in the users `~/.dolt` configuration.
@Hydrocharged can you take a look?
Note the merge of `main` into `test2` and then merge of 'test2` back into `main` both as `--no-ff` merges.
Good feature request. We'll consider and get back to you.
Both [`dolt diff`](https://docs.dolthub.com/cli-reference/cli#dolt-diff) on the command line and the [`dolt_patch()` function](https://docs.dolthub.com/sql-reference/version-control/dolt-sql-functions#dolt_patch) support the ability to filter to just schema changes. So, one could build a manual workflow to only commit...
Yes. We would definitely take a PR here.
Thanks for using `go-mysql-server` (GMS as we call it). I think you are correct that most of the issues you are seeing with drop and rename index are that the...