File: lock_tables_lost_commit.test

package info (click to toggle)
mysql-dfsg 4.0.24-10sarge3
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 56,212 kB
  • ctags: 42,312
  • sloc: ansic: 257,918; cpp: 93,002; perl: 29,480; sh: 24,628; tcl: 19,882; yacc: 3,558; makefile: 2,452; java: 2,300; awk: 1,484; asm: 687; sed: 428; sql: 27
file content (20 lines) | stat: -rw-r--r-- 503 bytes parent folder | download 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
 
# This is a test for bug 578

-- source include/have_innodb.inc

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

connection con1;
drop table if exists t1;
create table t1(a int) type=innodb;
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;