Tim Sehn
Tim Sehn
All other concurrent transactions work as traditional databases. You just have to single thread `dolt_merge()`.
I'm going to resolve because we gave you a workaround.
Gonna close as we have it working in the new format.
Dropping the database at the commit (ie. `drop database us_jails/asha5b6ut0cbaaouoo3pifle4dp3220g`) should be a suitable workaround if a customer runs into this.
@JCOR11599 did you fix this in your reserved words PR?
We need end to end tests like: https://github.com/dolthub/dolt/blob/main/integration-tests/bats/merge.bats https://github.com/dolthub/dolt/blob/main/integration-tests/bats/conflict-detection.bats https://github.com/dolthub/dolt/blob/main/integration-tests/bats/conflict-detection-2.bats But on the SQL path. I'll start on that.
Here's a more minimal repro: ``` create table state_populations (state varchar(14) not null,population int,rate \ double,primary key (state)); insert into state_populations (state, population, rate) values ('Delaware', 590\ 96, 0.98),('New Hampshire',...
Our bats tests are actually pretty good here. They just assume you shut autocommit off to do all the stuff.
There's a ton of complexity with the following: 1. autocommit on/off a. if off, open or closed transaction 2. batch mode on/off (ie. disable batch)
Dave, We've had a ton of discussion about this internally. As far as I understand, the idea is that you need to create and resolve conflicts in the same transaction....