File: gr_foreign_key_unique_conflict.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (85 lines) | stat: -rw-r--r-- 3,252 bytes parent folder | download
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
################################################################################
# Test case to verify that concurrent transactions with intersecting
# write set, on foreign key referencing not null unique key, do conflict.
#
# Test:
# 0. The test requires two servers: M1 and M2.
# 1. Create a table on server1.
# 2. Checking the negative case in which there is a conflict.
# 3. Checking the positive case in which there is no conflict.
# 4. Check the data sanity.
# 5. Clean up.
################################################################################

--source include/have_debug_sync.inc
--source include/have_group_replication_plugin.inc
--source include/group_replication.inc

--echo
--echo ############################################################
--echo # 1. Create a table on server1.
--let $rpl_connection_name= server1
--source include/rpl_connection.inc

CREATE TABLE t1 (c1 INT UNIQUE KEY NOT NULL);
CREATE TABLE t2 (c2 INT UNIQUE KEY NOT NULL, FOREIGN KEY (c2) REFERENCES t1(c1));
INSERT INTO t1 VALUES(1);
--source include/rpl_sync.inc

--echo
--echo ############################################################
--echo # 2. Checking the negative case in which there is a conflict.
--let $local_server_connection1=server1
--let $local_server_connection2=server_1
--let $remote_server_connection=server2
--let $local_transaction= INSERT INTO t2 VALUES (1)
--let $remote_transaction=UPDATE t1 SET c1=2 WHERE c1=1
--let $conflict_test=1
--source include/gr_parallel_local_and_remote_transactions.inc

--echo
--echo ############################################################
--echo # 3. Checking the positive case in which there is no conflict.
INSERT INTO t1 VALUES (5);

--let $local_server_connection1=server1
--let $local_server_connection2=server_1
--let $remote_server_connection=server2
--let $local_transaction= INSERT INTO t2 VALUES (5)
--let $remote_transaction=UPDATE t1 SET c1=6 WHERE c1=2
--let $conflict_test=0
--source include/gr_parallel_local_and_remote_transactions.inc

--echo
--echo ############################################################
--echo # 4. Check the data sanity.
--let $rpl_connection_name= server1
--source include/rpl_connection.inc

--let $assert_text= Table t2 will contain row after the above execution
--let $assert_cond= "[SELECT COUNT(*) AS count FROM t2 WHERE t2.c2 = 5, count, 1]" = "1"
--source include/assert.inc

--let $assert_text= Table t1 will contain row after the above execution
--let $assert_cond= "[SELECT COUNT(*) AS count FROM t1 WHERE t1.c1 = 5, count, 1]" = "1"
--source include/assert.inc

--let $assert_text= Table t1 will contain row after the above execution
--let $assert_cond= "[SELECT COUNT(*) AS count FROM t1 WHERE t1.c1 = 6, count, 1]" = "1"
--source include/assert.inc

--let $assert_text= Table t2 will contain 1 rows after the above execution
--let $assert_cond= "[SELECT COUNT(*) FROM t2]" = "1"
--source include/assert.inc

--let $assert_text= Table t1 will contain 2 rows after the above execution
--let $assert_cond= "[SELECT COUNT(*) FROM t1]" = "2"
--source include/assert.inc

--echo
--echo ############################################################
--echo # 5. Clean up.
DROP TABLE t2;
DROP TABLE t1;

--source include/group_replication_end.inc