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
|
#
# Simple test of the serial event log for single INSERT/DELETE statements
#
# We create a table and insert some records
# into it then delete a record.
#
# We then use the transaction_reader in drizzled/message/ to read the events.
#
--disable_warnings
DROP TABLE IF EXISTS t1;
--enable_warnings
CREATE TABLE t1 (
id INT NOT NULL
, padding VARCHAR(200) NOT NULL
, PRIMARY KEY (id)
);
INSERT INTO t1 VALUES (1, "I love testing.");
INSERT INTO t1 VALUES (2, "I hate testing.");
DELETE FROM t1 where id = 1;
DROP TABLE t1;
# Test the situation where no keys (WHERE clause)
# are specified in a DELETE statement. In the absence
# of triggers, this equates to a TRUNCATE TABLE statement,
# and this is what should be written to the transaction log,
# not multiple DeleteRecord events.
#
# However, right now this optimization does not occur. We
# write individual DeleteRecord message to the log. We will
# optimize this away once TableShare has been refactored
CREATE TABLE t1 (
id INT NOT NULL
, other INT NOT NULL
, PRIMARY KEY (id)
);
INSERT INTO t1 VALUES (1, 1);
INSERT INTO t1 VALUES (2, 2);
INSERT INTO t1 VALUES (3, 3);
INSERT INTO t1 VALUES (4, 4);
INSERT INTO t1 VALUES (5, 5);
INSERT INTO t1 VALUES (6, 6);
INSERT INTO t1 VALUES (7, 7);
INSERT INTO t1 VALUES (8, 8);
# This should produce a TRUNCATE event
DELETE FROM t1;
DROP TABLE t1;
|