Debian Codegraph @

storage/myisam/mysql-test/storage_engine/trx/select_for_update.rdiff

raw
1 --- suite/storage_engine/trx/select_for_update.result
2 +++ suite/storage_engine/trx/select_for_update.reject
3 @@ -1,3 +1,9 @@
4 +# -- WARNING ----------------------------------------------------------------
5 +# According to I_S.ENGINES, MyISAM does not support transactions.
6 +# If it is true, the test will most likely fail; you can
7 +# either create an rdiff file, or add the test to disabled.def.
8 +# If transactions should be supported, check the data in Information Schema.
9 +# ---------------------------------------------------------------------------
10 DROP TABLE IF EXISTS t1;
11 CREATE TABLE t1 (a <INT_COLUMN>, b <CHAR_COLUMN>) ENGINE=<STORAGE_ENGINE> <CUSTOM_TABLE_OPTIONS>;
12 INSERT INTO t1 (a,b) VALUES (1,'a'),(2,'b'),(3,'a');
13 @@ -14,16 +20,33 @@
14 1 a
15 3 a
16 SELECT a,b FROM t1 WHERE b='a' LOCK IN SHARE MODE;
17 -ERROR HY000: Lock wait timeout exceeded; try restarting transaction
18 +a b
19 +1 a
20 +3 a
21 +# ERROR: Statement succeeded (expected results: ER_LOCK_WAIT_TIMEOUT)
22 +# ------------ UNEXPECTED RESULT ------------
23 +# The statement|command succeeded unexpectedly.
24 +# SELECT .. FOR UPDATE or LOCK IN SHARE MODE or the mix could be unsupported|malfunctioning, or the problem was caused by previous errors.
25 +# You can change the engine code, or create an rdiff, or disable the test by adding it to disabled.def.
26 +# Further in this test, the message might sometimes be suppressed; a part of the test might be skipped.
27 +# Also, this problem may cause a chain effect (more errors of different kinds in the test).
28 +# -------------------------------------------
29 UPDATE t1 SET b='c' WHERE b='a';
30 -ERROR HY000: Lock wait timeout exceeded; try restarting transaction
31 +# ERROR: Statement succeeded (expected results: ER_LOCK_WAIT_TIMEOUT)
32 +# ------------ UNEXPECTED RESULT ------------
33 +# The statement|command succeeded unexpectedly.
34 +# UPDATE or SELECT .. FOR UPDATE or the mix could be unsupported|malfunctioning, or the problem was caused by previous errors.
35 +# You can change the engine code, or create an rdiff, or disable the test by adding it to disabled.def.
36 +# Further in this test, the message might sometimes be suppressed; a part of the test might be skipped.
37 +# Also, this problem may cause a chain effect (more errors of different kinds in the test).
38 +# -------------------------------------------
39 connection con1;
40 COMMIT;
41 SELECT a,b FROM t1;
42 a b
43 -1 a
44 +1 c
45 2 b
46 -3 a
47 +3 c
48 disconnect con1;
49 connection default;
50 UPDATE t1 SET b='c' WHERE b='a';