github dolthub/dolt v0.27.3
0.27.3
on GitHub

latest releases: v1.43.13, v1.43.12, v1.43.11...
3 years ago

Merged PRs

dolt

  • 2009: fix concurrent map edit issue
  • 2004: Regression test for issue 1131
  • 2003: Added Dolt Revert
    If any conflicts or constraints are generated then the revert is aborted. Git handles these as a special merge case (with a special git revert --abort command and all). Additionally, if multiple commits are specified then they're all reverted in a single commit (versus Git reversing each commit in a separate commit).
  • 1999: Removed hard-coded html in docs for sql-server command
    Identified by #845
  • 1998: Bats test for return code behavior of checking out current branch
    Fixes #836
  • 1996: Skipped test for error when resetting a renamed table
    This reproduces the failures in #751
  • 1994: Added a test for git config and HOME env var
    Fixes #562
  • 1993: Fix and unskip keyword test
    This fixes #560
  • 1986: Andy/auto increment refactor
  • 1985: go/libraries/doltcore/env/actions/commitwalk: Optimize commitwalk a bit.
  • 1983: Update BATS README
    Add the prerequisites to running bats tests to the README
  • 1982: go/go.mod: Bump fslock.
  • 1976: Cleanup from transaction migration
    First batch of cleanup, getting rid of uses of RepoStateWriter as much as possible.
    To push this farther requires new abstractions that can handle updating the HEAD, head commit, and working roots at the same time, which is the next step.
  • 1974: Optimize merge by skipping tables without edits
    10x speedup for the Nautobot database:
    before: 
    % time dolt --prof cpu merge add-ipaddress
Updating uaimen5cq6jucq3abr85klgj0g594qc1..d3922cbd8fop4ast7ohl9mm4d3dn3632
extras_objectchange | 1 +
ipam_ipaddress      | 1 +
2 tables changed, 2 rows added(+), 0 rows modified(*), 0 rows deleted(-)
dolt --prof cpu merge add-ipaddress  83.78s user 3.75s system 567% cpu 15.433 total
    after: 
    % time dolt --prof cpu merge add-ipaddress
Updating uaimen5cq6jucq3abr85klgj0g594qc1..d3922cbd8fop4ast7ohl9mm4d3dn3632
extras_objectchange | 1 +
ipam_ipaddress      | 1 +
2 tables changed, 2 rows added(+), 0 rows modified(*), 0 rows deleted(-)
dolt --prof cpu merge add-ipaddress  2.27s user 0.17s system 158% cpu 1.545 total
  • 1938: Bh/gen cs

go-mysql-server

  • 519: Fix explicit DEFAULT value in insert query
    It seems that go-mysql-server is not compatible with insert query like: 
    INSERT INTO `users` (`id`, `deleted`) VALUES (1, DEFAULT)
    Whereas DEFAULT is just to specify deleted columns should use column default value explicitly.
    The issue could be demostrated using below code: 
    package main
import (
dbsql "database/sql"
sqle "github.com/dolthub/go-mysql-server"
"github.com/dolthub/go-mysql-server/auth"
"github.com/dolthub/go-mysql-server/memory"
"github.com/dolthub/go-mysql-server/server"
_ "github.com/go-sql-driver/mysql"
)
func main() {
db, _ := dbsql.Open("mysql", "root:@tcp(127.0.0.1:3307)/test")
defer db.Close()
query := `CREATE TABLE users (
id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
deleted tinyint(1) unsigned NOT NULL DEFAULT '0',
PRIMARY KEY (id)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=utf8mb4`
stmt, _ := db.Prepare(query)
stmt.Exec()
_, err := db.Exec("INSERT INTO `users` (`id`, `deleted`) VALUES (1, DEFAULT)")
if err != nil {
panic(err.Error())
}
stmtOut, _ := db.Prepare("SELECT `deleted` FROM `users` WHERE `id` = 1")
defer stmtOut.Close()
deleted := true
err = stmtOut.QueryRow().Scan(&deleted)
if err != nil {
panic(err.Error())
}
if deleted == true {
panic("Wrong deleted value")
}
}
var engine *sqle.Engine
func init() {
engine = sqle.NewDefault()
db := memory.NewDatabase("test")
engine.AddDatabase(db)
config := server.Config{
Protocol: "tcp",
Address:  "localhost:3307",
Auth:     auth.NewNativeSingle("root", "", auth.AllPermissions),
}
s, _ := server.NewDefaultServer(config, engine)
go s.Start()
}
    `db.Exec("INSERT INTO `users` (`id`, `deleted`) VALUES (1, DEFAULT)")` will result in error:
Error 1105: plan is not resolved because of node '*plan.Values'
    This pull request should avoid such issue by turning explicit DEFAULT in insert query to implicit.

vitess

  • 83: Max/drop pk

Closed Issues

  • 2008: Generational NBS Concurrent Map Writes Panic
  • 579: Support multiple concurrent connections modifying the working set in SQL server
  • 1795: Quickstart install requires executing remote code as root
  • 1823: dolt fetch prints many empty lines to terminal
  • 1817: Add more features to CREATE TABLE SELECT
  • 1772: Should be a parse error
  • 1684: dolt clone errors due to timeout on poor connections
  • 1564: Add commit hash functionality to dolt ls --verbose
  • 1551: dolt sql --multi-db-dir does not ignore broken dolt repositories
  • 1774: write_file and write_pandas raise DoltException on Windows
  • 1520: Certain JOINS Unexpectedly take a lot of time
  • 1609: Binary Bug Asked To Be Submitted By Zachmu (Dolt v0.26.2)
  • 1428: Support CONSTRAINT ... PRIMARY KEY syntax in CREATE TABLE
  • 1388: Dolt : SQL queries : via a JavaScript library!
  • 1383: Bad error message for ALTER TABLE error
  • 1969: feature request: dolt commit revert
  • 1340: DOLT SQL Functions Need Additional Testing for Autocommit
  • 1320: UPDATES in shell that throw errors occasionally return changes (e.g. diff is non-empty)
  • 1319: You can delete every branch in Dolt from SQL
  • 1227: Windows paths not understood by dolt add in Powershell
  • 1173: Reset hard does not delete newly created docs (ex. readme(
  • 1160: dolt sql-server runs on occupied port
  • 1154: Views broken starting in v0.22.7 for coronavirus dataset
  • 1131: Weird Index bug
  • 562: dolt does not respect the $HOME env var
  • 1135: Match MySQL on execution order when missing ORDER BY clause
  • 1114: LIKE returns bad results
  • 1054: dolt_commit_ancestors causes Python 8.0.21 connector to throw unknown error
  • 1006: Accept more date formats
  • 1004: CREATE INDEX requires case-sensitive column names
  • 964: Editing database in a separate process with server running causes weird ODBC connection error
  • 963: benchmark for full table scan
  • 880: Index lookups on timestamp columns don't work
  • 879: Make timestamp and date columns directly comparable with string literals
  • 846: dolt sql-server --help should mention the way databases are specified
  • 898: Don't require quoting AS OF expressions for branch names, hashes
  • 836: Match Git exit codes when checking out current branch
  • 815: Use-Case proposition: Machine Learning Ground Truth Curation
  • 833: mysql-connector-python fails to connect to dolt sql-sever
  • 810: Dropping and creating a table with the same name creates a peculiar status message
  • 808: feature: GPT-3 integration
  • 798: Dolt CLI does not recognize tables created in an active SQL shell session
  • 792: Filters do not seem to be functioning properly on Dolt history tables
  • 501: Add Dolt login hints to permission denied erros
  • 756: From User: No way to dolt fetch/merge/push against sql-server via SQL/odbc
  • 742: dolt should look for .dolt directory in descending directory tree
  • 739: Schema and ColCollection
  • 722: Bug in documentation caused by being in a repo
  • 720: Save query succeeds with dud input
  • 718: dolt push behavior does not seem to match docs
  • 717: dolt schema export doesn't have a commit option
  • 593: dolt schema import assigns sequential tags starting at 0. Sure to cause tag collisions if importing multiple tables.
  • 580: tighter coupling of GitHub release tags and commit graph
  • 560: Valid SQL column names are not handled correctly by dolt sql
  • 532: Long running queries on dolthub.com timeout with confusing UI error message
  • 520: Dolt SQL: Support 'on duplicate key update'
  • 504: Remote requests on sql commands
  • 477: Strange error message when a column has been dropped
  • 464: dolt_docs to conform to other feature tables
  • 442: Panic using dolt push --set-upstream
  • 440: Update with a datetime field not behaving correctly
  • 410: Broken JSON import
  • 405: Sub-select has no access to variable in external scope
  • 397: Panic in SQL when WHERE clause uses computed column
  • 1611: Run a remote Dolt, perhaps several
  • 374: Reordering columns can get table to invalid state (no primary key)
  • 314: SQL shell must be reloaded to write to newly created columns
  • 309: dolt clone has bad error message when not logged in
  • 226: piping large .sql files requires significant memory
  • 141: Dolt SQL shell backspace weirdness
  • 53: Can create empty column name using appropriately formatted CSV
  • 1641: Dolt: dolt login will create new credentials even when I'm already logged in
  • 1615: Git-Dolt: Consider changing pointer file format to JSON
  • 1627: Dolt: For large imports, need some sort of progress output
  • 1633: dolt: dolt push when behind your remote returns 0 exit code. should be 1
  • 1635: dolt: dolt config --list does not respect local overrides
  • 1973: dolt merge --abort and DOLT_MERGE("--abort"); do not reset staging index
  • 1977: Creating Boolean type field in table in dolthub UI fails.
  • 480: any performance benchmark for dolt?
  • 517: can someone pls provide the instructions on how to port rocksdb as storage backend?
Check out latest releases or
releases around dolthub/dolt v0.27.3

Don't miss a new dolt release

NewReleases is sending notifications on new releases.

Get notifications