Nick Tobey
Nick Tobey
Sometimes when merges fail, there's more context / nuance than can reasonably be displayed in an error message. The motivating example here is a case where a branch contains changes...
MySQL allows indexes to be defined using expressions, as described here: https://dev.mysql.com/doc/refman/8.0/en/create-index.html#create-index-functional-key-parts The main benefit of this is that is allows the engine to use these indexes when the same...
Secondary indexes on in-memory tables are currently not very efficient: they're stored as a sorted list of rows, and don't get re-sorted until the end of a batch table edit...
This adds a new message/node type: Vector Index, and a corresponding prolly-tree-based map structure: the Proximity Map The Vector Index message currently has a subset of the Prolly Map message....
Repro: ``` dolt init dolt sql -q "create table test(pk int primary key, g int as (pk*pk));" dolt sql -q "insert into test(pk) values (1);" dolt dump -f -fn ~/dump.sql...
Example 1: ``` create table test(pk int primary key, j int, value int as (pk*pk)); insert into test(pk, j) values (-1, 1), (2, 1), (-3, 1); select value from test...