SQL Reference
CLI Reference
Architecture
Conflicts
What is a Conflict?
A conflict is a signal to a user that a merge has produced a database that requires further action. The merge algorithm could not infer the state of the database based on the merge rules after the merge. Further input is required to tell Dolt what the resulting merged database should contain.
In Dolt, conflicts can occur on schema and data.
Data
On data, conflicts are detected on a cell-level. If two operations modify the same row, column pair to be different values, a conflict is detected.
Schema
For schema, conflict detection is more complicated. The following rules are used to detect conflicts in schema:
- 1.If two branches add the same table, no conflict.
- 2.If two branches add a similarly named table that has different schema, conflict.
- 3.If the two merged branches add two differently named columns to the same table, no conflict.
- 4.If the two merged branches add similarly named columns to the same table with the same data, no conflict.
- 5.If the two merged branches add similarly named columns in the same table with different data, conflict.
- 6.If one branch deletes a column and the other branch does not modify that column in the same table, no conflict.
- 7.If one branch deletes a column and the other branch modifies that column in the same table, conflict.
- 8.If the two branches alter a column similarly in the same table, no conflict.
- 9.If two branches alter a column differently in the same table, conflict.
How to use Conflicts
Conflicts signal to the user that a merge is risky. In the event of a conflict, you can either redo the changes on the tip of the branch you are merging into or resolve the conflicts.
In the case of conflict resolution Dolt supports two automated resolution strategies, ours or theirs. You can choose to keep the state of schema or data on the branch you are on or the branch you are merging.
If you would like to manually resolve conflicts, you can set the value of the row that has the conflict to whatever you would like and then resolve the conflict by deleting the corresponding conflict row in
dolt_conflicts_<tablename>.Difference between Git conflicts and Dolt conflicts
Conflicts are a major divergence from Git in Dolt. Conceptually, Dolt and Git conflicts are similar, but in practice Dolt the Dolt conflict management workflow and user interface is very different.
In Dolt, conflicts are stored in the
dolt_conflicts set of tables. Each table in your database has an associated dolt_conflicts table. For instance if you have a table named docs, there is a system table named dolt_conflicts_docs. This replaces the >>> and <<< syntax that is inserted into your files in Git when conflicts occur.Dolt conflicts can occur on schema or data. In Git, conflicts can only occur on lines in files. So Dolt has two types of conflicts whereas Git has one type.
In the case of foreign keys, Dolt can produce invalid merges even after conflicts are resolved. In Dolt, this merge will not be able to be committed until the foreign key violations are resolved. In Git, a repository with no conflict markers is a valid repository and can be committed.
Example
Generating a Conflict
1
docs $ dolt sql -q "select * from docs"
2
+----+----+
3
| pk | c1 |
4
+----+----+
5
| 0 | 0 |
6
| 1 | 1 |
7
| 2 | 2 |
8
+----+----+
9
docs $ dolt branch make-conflicts
10
docs $ dolt sql -q "update docs set c1=10 where pk=1"
11
Query OK, 1 row affected
12
Rows matched: 1 Changed: 1 Warnings: 0
13
docs $ dolt sql -q "select * from docs"
14
+----+----+
15
| pk | c1 |
16
+----+----+
17
| 0 | 0 |
18
| 1 | 10 |
19
| 2 | 2 |
20
+----+----+
21
docs $ dolt add docs
22
docs $ dolt commit -m "Made pk=1, c1=10"
23
commit jjkqslpnbbvjh7efdhcsqdh68ekl0leb
24
Author: Tim Sehn <[email protected]>
25
Date: Mon Dec 06 16:40:12 -0800 2021
26
​
27
Made pk=1, c1=10
28
​
29
docs $ dolt checkout make-conflicts
30
Switched to branch 'make-conflicts'
31
docs $ dolt sql -q "select * from docs"
32
+----+----+
33
| pk | c1 |
34
+----+----+
35
| 0 | 0 |
36
| 1 | 1 |
37
| 2 | 2 |
38
+----+----+
39
docs $ dolt sql -q "update docs set c1=0 where pk=1"
40
Query OK, 1 row affected
41
Rows matched: 1 Changed: 1 Warnings: 0
42
docs $ dolt sql -q "select * from docs"
43
+----+----+
44
| pk | c1 |
45
+----+----+
46
| 0 | 0 |
47
| 1 | 0 |
48
| 2 | 2 |
49
+----+----+
50
docs $ dolt add docs
51
docs $ dolt commit -m "Made pk=1, c1=0"
52
commit 5gmleh5ksmtsdeeaqeagpsitpug4ntoj
53
Author: Tim Sehn <[email protected]>
54
Date: Mon Dec 06 16:40:54 -0800 2021
55
​
56
Made pk=1, c1=0
57
​
58
docs $ dolt checkout main
59
Switched to branch 'main'
60
docs $ dolt merge make-conflicts
61
Updating jjkqslpnbbvjh7efdhcsqdh68ekl0leb..5gmleh5ksmtsdeeaqeagpsitpug4ntoj
62
Auto-merging docs
63
CONFLICT (content): Merge conflict in docs
64
Automatic merge failed; fix conflicts and then commit the result.
65
docs $ dolt conflicts cat docs
66
+-----+--------+----+----+
67
| | | pk | c1 |
68
+-----+--------+----+----+
69
| | base | 1 | 1 |
70
| * | ours | 1 | 10 |
71
| * | theirs | 1 | 0 |
72
+-----+--------+----+----+
Copied!
Resolving a Conflict
1
docs $ dolt conflicts cat docs
2
+-----+--------+----+----+
3
| | | pk | c1 |
4
+-----+--------+----+----+
5
| | base | 1 | 1 |
6
| * | ours | 1 | 10 |
7
| * | theirs | 1 | 0 |
8
+-----+--------+----+----+
9
docs $ dolt conflicts resolve --ours docs
10
docs $ dolt conflicts cat docs
11
docs $ dolt sql -q "select * from docs"
12
+----+----+
13
| pk | c1 |
14
+----+----+
15
| 0 | 0 |
16
| 1 | 10 |
17
| 2 | 2 |
18
+----+----+
19
docs $ dolt add docs
20
docs $ dolt commit -m "Resolved conflict"
21
commit c8mff2tp5b3tg4j4u07dnmp912btltim
22
Merge: jjkqslpnbbvjh7efdhcsqdh68ekl0leb 5gmleh5ksmtsdeeaqeagpsitpug4ntoj
23
Author: Tim Sehn <[email protected]>
24
Date: Mon Dec 06 16:44:22 -0800 2021
25
​
26
Resolved conflict
Copied!
Last modified 18d ago
Export as PDF
Copy link
Edit on GitHub