File: lock_tables_lost_commit.test

package info (click to toggle)
mariadb-10.0 10.0.32-0%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 476,064 kB
  • sloc: cpp: 1,400,131; ansic: 832,140; perl: 54,391; sh: 41,304; pascal: 32,365; yacc: 14,921; xml: 5,257; sql: 4,667; cs: 4,647; makefile: 4,555; ruby: 4,465; python: 2,292; lex: 1,427; java: 941; asm: 295; awk: 54; php: 22; sed: 16
file content (33 lines) | stat: -rw-r--r-- 845 bytes parent folder | download | duplicates (18)
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
# Test for Bug#578 mysqlimport -l silently fails when binlog-ignore-db is set

--source include/have_innodb.inc

# Save the initial number of concurrent sessions
--source include/count_sessions.inc

connect (con1,localhost,root,,);
connect (con2,localhost,root,,);

connection con1;
--disable_warnings
DROP TABLE IF EXISTS t1;
CREATE TABLE t1(a INT) ENGINE=innodb;
--enable_warnings
LOCK TABLES t1 WRITE;
INSERT INTO t1 VALUES(10);
disconnect con1;

connection con2;
# The bug was that, because of the LOCK TABLES, the handler "forgot" to commit,
# and the other commit when we write to the binlog was not done because of
# binlog-ignore-db
SELECT * FROM t1;
DROP TABLE t1;

connection default;
disconnect con2;

# End of 4.1 tests

# Wait till we reached the initial number of concurrent sessions
--source include/wait_until_count_sessions.inc