Concepts
SQL Reference
CLI Reference
Architecture
Querying History
Dolt databases allow you to query the data at any point in the commit history. There are several ways to do so.
Please note: when querying history, the unit of snapshot is the dolt commit. SQL transaction commits do not create a dolt commit by default.
Querying past snapshots with AS OF
AS OFDolt SQL supports a variant of SQL 2011 syntax to query non-HEAD revisions of a database via the
AS OF clause:1
SELECT * FROM myTable AS OF 'kfvpgcf8pkd6blnkvv8e0kle8j6lug7a';
2
SELECT * FROM myTable AS OF 'myBranch';
3
SELECT * FROM myTable AS OF 'HEAD^2';
4
SELECT * FROM myTable AS OF TIMESTAMP('2020-01-01');
5
SELECT * FROM myTable AS OF 'myBranch' JOIN myTable AS OF 'yourBranch' AS foo;
Copied!
The
AS OF expression must name a valid Dolt reference, such as a commit hash, branch name, or other reference. Timestamp / date values are also supported. Each table in a query can use a different AS OF clause.In addition to this
AS OF syntax for SELECT statements, Dolt also supports various extensions to the standard MySQL syntax to examine the schemas of snapshots:1
SHOW TABLES AS OF 'kfvpgcf8pkd6blnkvv8e0kle8j6lug7a';
2
SHOW CREATE TABLE myTable AS OF 'myBranch';
3
DESCRIBE myTable AS OF 'HEAD~';
Copied!
Specifying a commit hash for an entire connection
You can connect to a non-HEAD, read-only database where every table is locked to a particular commit. Use a connection string like this:
mysql://127.0.0.1:3306/mydb/ia1ibijq8hq1llr7u85uivsi5lh3310pOr a
USE statement. Note the backtick quoting, which is necessary since the database identifier contains a slash character.1
USE `mydb/ia1ibijq8hq1llr7u85uivsi5lh3310p`
Copied!
Or specify the commit hash directly in the query. This is equivalent to
AS OF, but works in some queries where the AS OF syntax is not supported.1
show create table `mydb/ia1ibijq8hq1llr7u85uivsi5lh3310p`.myTable;
Copied!
Querying history using dolt system tables
For every table in the database, dolt also provides a set of system tables that you can query to see past values of rows, diffs between revisions, and more.
the
dolt_history tables provide a row for every revision of a row in a table.1
SELECT * FROM dolt_history_mytable
2
WHERE state = "Virginia"
3
ORDER BY "commit_date"
4
​
5
+----------+------------+----------+-------------+-----------+---------------------------------+
6
| state | population | capital | commit_hash | committer | commit_date |
7
+----------+------------+----------+-------------+-----------+---------------------------------+
8
| Virginia | 691937 | NULL | ... | billybob | 1790-01-09 00:00:00.0 +0000 UTC |
9
| Virginia | 807557 | Richmond | ... | billybob | 1800-01-01 00:00:00.0 +0000 UTC |
10
| Virginia | 877683 | NULL | ... | billybob | 1810-01-01 00:00:00.0 +0000 UTC |
11
+----------+------------+----------+-------------+-----------+---------------------------------+
Copied!
To query how rows changed between two commits, use the
dolt_commit_diff and dolt_diff tables.1
SELECT * FROM dolt_commit_diff_mytable
2
WHERE to_commit = HASHOF('HEAD')
3
AND from_commit = HASHOF('HEAD~')
4
ORDER BY state, to_commit_date;
Copied!
Querying historical view data
Database views are an edge case for historical queries. When you have a database view whose definition has changed, querying it with
AS OF will use the current definition of the view, but use rows from the tables as they existed at the revision provided.To query the historical definition of a view, you must checkout the database at a particular commit. You can do this by changing your branch, e.g.:
1
select dolt_checkout('-b', 'old-view-def', '81223g1cpmib215gmov8686b6310p37d');
Copied!
You can also do this without changing your session's branch by using a commit hash-qualified database identifier when referencing the view.
Consider this example:
1
-- Past data
2
view_test> select * from t1 as of '81223g1cpmib215gmov8686b6310p37d';
3
+---+---+
4
| a | b |
5
+---+---+
6
| 1 | 1 |
7
| 2 | 2 |
8
+---+---+
9
-- Past view definition
10
view_test> show create table `view_test/81223g1cpmib215gmov8686b6310p37d`.v1;
11
+------+--------------------------------------+
12
| View | Create View |
13
+------+--------------------------------------+
14
| v1 | CREATE VIEW `v1` AS select * from t1 |
15
+------+--------------------------------------+
16
-- Current data
17
view_test> select * from t1;
18
+---+---+
19
| a | b |
20
+---+---+
21
| 1 | 1 |
22
| 2 | 2 |
23
| 3 | 3 |
24
+---+---+
25
-- Current view definition
26
view_test> show create table v1;
27
+------+-----------------------------------------------+
28
| View | Create View |
29
+------+-----------------------------------------------+
30
| v1 | CREATE VIEW `v1` AS select a+10, b+10 from t1 |
31
+------+-----------------------------------------------+
32
-- Select past data using current view definition
33
view_test> select * from v1 as of '81223g1cpmib215gmov8686b6310p37d';
34
+------+------+
35
| a+10 | b+10 |
36
+------+------+
37
| 11 | 11 |
38
| 12 | 12 |
39
+------+------+
40
-- Select past data using past view definition
41
view_test> select * from `view_test/81223g1cpmib215gmov8686b6310p37d`.v1;
42
+---+---+
43
| a | b |
44
+---+---+
45
| 1 | 1 |
46
| 2 | 2 |
47
+---+---+
48
-- Select past data using past view definition by checking out a new branch
49
view_test> select dolt_checkout('-b', 'old-view-def', '81223g1cpmib215gmov8686b6310p37d');
50
view_test> select * from v1;
51
+---+---+
52
| a | b |
53
+---+---+
54
| 1 | 1 |
55
| 2 | 2 |
56
+---+---+
Copied!
Last modified 1mo ago
Export as PDF
Copy link
Edit on GitHub