Neil Macneale IV

User tripped over this: https://github.com/dolthub/dolt/issues/7548

An observation: ``` prod_replication_test> set @@persist.dolt_replicate_to_remote = 'origin'; prod_replication_test> show variables like 'dolt_replicate_to_remote'; +--------------------------+-------+ | Variable_name | Value | +--------------------------+-------+ | dolt_replicate_to_remote | | +--------------------------+-------+ 1 row in set (0.00...

I'm able to repro this. There related bug (feature request) is that the sql-server doesn't get in sync when is starts and it's already ahead of the origin. That would...

User tripped on this: https://github.com/dolthub/dolt/issues/7548

Based on the commands above, I believe the issue is that you have a `dolt sql-server` instances which is running. The `dolt remote` command is unfortunately not handling that situation...

Hmm. You are supposed to get an error message which tells you to stop `sql-server` in cases like this. I'll test.

There are a couple bugs here, probably not the answer you wanted. First, the table and docs commands should simply tell you what you are attempting is impossible and requires...

Actually, the `dolt table rm` command does go through the SQL interface, which is correct. It's in a round about way though and I'm going to disable it since the...

Having a seperate ticket for each command wouldn't make this much better. If @verdverm is seeing the same error for all of them, then it's really one bug. That said,...

User tripped on this: https://github.com/dolthub/dolt/issues/7548