File: test_transactional_sequences.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 (86 lines) | stat: -rw-r--r-- 1,318 bytes parent folder | download | duplicates (3)
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
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
# name: test/sql/transactions/test_transactional_sequences.test
# description: Test that sequences are transactional
# group: [transactions]

# start a transaction for both nodes
statement ok con1
BEGIN TRANSACTION

statement ok con2
BEGIN TRANSACTION

# create a sequence in node one
statement ok con1
CREATE SEQUENCE seq;

# node one can see it
query I con1
SELECT nextval('seq');
----
1

# node two can't see it
statement error con2
SELECT nextval('seq');
----

# we commit the sequence
statement ok con1
COMMIT

# node two still can't see it
statement error con2
SELECT nextval('seq');
----

# now commit node two
statement ok con2
COMMIT

# we can now see the sequence in node two
query I con2
SELECT nextval('seq');
----
2

# drop sequence seq in a transaction
statement ok con1
BEGIN TRANSACTION

statement ok con1
DROP SEQUENCE seq;

# node one can't use it anymore
statement error con1
SELECT nextval('seq');
----

# node two can still use it
query I con2
SELECT nextval('seq');
----
3

# rollback cancels the drop sequence
statement ok con1
ROLLBACK;

# we can still use it
query I con2
SELECT nextval('seq');
----
4

# now we drop it for real
statement ok con1
DROP SEQUENCE seq;

# we can't use it anymore
statement error con1
SELECT nextval('seq');
----

statement error con2
SELECT nextval('seq');
----