Nick Tobey

> If you create a non-versioned table t on branch main, but then switch to myBranch which has another table t, we are left with a name collision to deal...

> Additional Dolt-specific design question exist such as whether these tables are stored in the commit graph and whether they're replicated. So there's two different interpretations here: replicated across branches...

Fixed by https://github.com/dolthub/dolt/pull/5809

One detail to note is that we currently desalinize JSON prior to writing it on the wire, so that we can re-serialize it in a way that matches MySQL's output...

We're tracking progress on this with https://github.com/dolthub/dolt/issues/6194, going to close this as a duplicate.

"First milestone is released: reads of dolt_branches get their data from the database's state at transaction start time." I'm noticing behavior that seems odd (to me), and I want to...

https://github.com/dolthub/dolt/pull/7118 implements the collation change side of this, but not the charset change side.

> How to remove secondary index data from an existing commit? Commit IDs are computed based on the stored data (including the secondary index data) so changing an existing commit...

The current comparison algorithm looks like this: 1. Find all keys shared by both objects and sort them lexographically. 2. Compare the values for these keys in sorted order. 3....

It looks like in this specific case (simultaneous modification and deletion of a table), the code doesn't consider it a conflict, it just considers it an error and aborts the...