Tim Sehn
Tim Sehn
So starting from a fresh database and remote works. ``` $ cd test_read_tables $ dolt init --fun Successfully initialized dolt data repository. $ dolt sql
It looks like this is only DoltHub remotes: ``` $ dolt remote -v origin https://doltremoteapi.dolthub.com/timsehn/sql_alchemy_demo $ dolt read-tables --dir tables_are_read_from_remote_alias origin main Dolt command 'read-tables' is not supported in format...
This is complicated because if you have access to the commit log, you can create a new branch that you can read from from a potentially restricted commit on another...
It is also fine to have the access controls only exist for SQL Server, not the built-in remote server.
This PR (#6040) makes it so bats only runs on `__DOLT__` with chunk journal enabled (the defaults).
A series of PRs in [1.2.1](https://github.com/dolthub/dolt/releases/tag/v1.2.1) removed testing code that was not testing old format any more. The next step here is to remove performance testing.
Great find. @elianddb will get on this today. I'm not certain why the schema diff is picking up an index change here.
Thanks for the additional repro steps. This should give something for @elianddb to chew on today.
I'm going to move this to GMS since it is GMS specific.
This is a weird one. I'm not sure why temptf would get so large. This is an @reltuk question.