File: test_cascading_updates.test

package info (click to toggle)
duckdb 1.5.1-2
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 299,196 kB
  • sloc: cpp: 865,414; ansic: 57,292; python: 18,871; sql: 12,663; lisp: 11,751; yacc: 7,412; lex: 1,682; sh: 747; makefile: 558
file content (71 lines) | stat: -rw-r--r-- 1,151 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
# name: test/sql/update/test_cascading_updates.test
# description: Test many different updates
# group: [update]

load __TEST_DIR__/cascading_updates.db

statement ok
SET default_null_order='nulls_first';

statement ok
SET immediate_transaction_mode=true

statement ok con1
BEGIN

statement ok
CREATE TABLE integers(id INTEGER, val INTEGER);

statement ok
INSERT INTO integers SELECT i, i FROM range(10000) t(i)

statement ok
PRAGMA checkpoint_threshold='1GB'

statement ok
UPDATE integers SET val=val+1000000 WHERE id=1

statement ok con2
BEGIN

statement ok
UPDATE integers SET val=val+1000000 WHERE id=2

statement ok con3
BEGIN

statement ok
UPDATE integers SET val=val+1000000 WHERE id=3

statement ok con1
COMMIT

query I
SELECT COUNT(*) FROM integers WHERE val>1000000
----
3

# we cannot checkpoint because con2/con3 rely on older changes
statement error
CHECKPOINT
----
Cannot CHECKPOINT

# after committing, we can checkpoint
statement ok con2
COMMIT

statement ok con3
COMMIT

# even if con2 is active, we can still checkpoint
statement ok con2
BEGIN

statement ok
CHECKPOINT

query I
SELECT COUNT(*) FROM integers WHERE val>1000000
----
3