Tim Sehn comments

Results 334 comments of


                                            Tim Sehn

Incorrect result from aggregating on table joined in both subquery and CTE

Note, Max ran the queries in with`dolt sql`and they all seem to work/return the same results: So, we also suspect some sort of client issue. We need more information to...

Incorrect result from aggregating on table joined in both subquery and CTE

We love the report! Just want to get it fixed for you :-)

`dolt merge` silently violates check constraints

Slight mod to the repro: ``` dolt sql

`dolt merge` silently violates check constraints

We do check foreign key and unique key constraints on merge.

`dolt diff --summary` with cell-wise statistics

This means changing this, a single column table with one row added: ``` test_drop_constraint $ dolt diff --summary diff --dolt a/t b/t --- a/t @ dhvdp8ur16g6mrkqia1m5nofb3oqnldd +++ b/t @ 4ovq7l6evjbl5t0mfct7165t3ac90ece...

`dolt diff --summary` with cell-wise statistics

@jennifersp is going to add this as she works on this one: https://github.com/dolthub/dolt/issues/4043

Prevent altering table tables to have `FULLTEXT` key property

Example: ``` test-fk-indexes $ dolt sql -q "create table t (a int primary key, b int)" test-fk-indexes $ dolt sql -q "alter table t modify column b int fulltext key;"...

Prevent altering table tables to have `FULLTEXT` key property

Resolving this in favor of #2987. We allow you to define some DDL we don't support on a table for `mysqldump` compatibility.

`dolt_conflicts_resolve()` SQL procedure

dolt_conflicts_resolve() matches the CLI interface.

`dolt la` doesn't work

Thanks. We're not focused on the CLI right now. We're more focused on the database/SQL use case. But this is a good feature request, We just won't get to it...