File: lock_tables_lost_commit.test

package info (click to toggle)
mysql-dfsg-4.1 4.1.11a-4sarge8
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 86,724 kB
  • ctags: 78,396
  • sloc: ansic: 380,120; cpp: 348,266; sh: 32,501; tcl: 30,484; perl: 20,873; yacc: 5,447; java: 4,610; makefile: 4,406; xml: 3,857; pascal: 1,795; awk: 1,338; asm: 1,064; sed: 772; sql: 503
file content (22 lines) | stat: -rw-r--r-- 542 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
 
# This is a test for bug 578

-- source include/have_innodb.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;