mirror of
https://github.com/MariaDB/server.git
synced 2025-01-17 12:32:27 +01:00
9a202517f5
(back to behaviour of 4.1.7). Warning was not fatal: mysqldump continued. And the good thing is that it helped spot that starting from 4.1.7, SHOW CREATE DATABASE failed (if --single-transaction and first db has non-empty InnoDB table and there is a second db) and thus mysqldump produced CREATE DATABASE statements missing the CHARACTER SET clause. Removing the bug which was in the server, and the warning reporting in mysqldump (compatibility with old servers). client/mysqldump.c: don't report errors as we deal almost gracefully with them (back to code of 4.1.7) mysql-test/r/flush_block_commit.result: result update mysql-test/t/flush_block_commit.test: let's verify that SHOW CREATE DATABASE succeeds even if connection has open transaction. sql/sql_parse.cc: There is no reason to forbid SHOW CREATE DATABASE if connection has an open transaction
39 lines
630 B
Text
39 lines
630 B
Text
drop table if exists t1;
|
|
create table t1 (a int) engine=innodb;
|
|
begin;
|
|
insert into t1 values(1);
|
|
flush tables with read lock;
|
|
select * from t1;
|
|
a
|
|
commit;
|
|
select * from t1;
|
|
a
|
|
unlock tables;
|
|
begin;
|
|
select * from t1 for update;
|
|
a
|
|
1
|
|
begin;
|
|
select * from t1 for update;
|
|
flush tables with read lock;
|
|
commit;
|
|
a
|
|
1
|
|
unlock tables;
|
|
commit;
|
|
begin;
|
|
insert into t1 values(10);
|
|
flush tables with read lock;
|
|
commit;
|
|
unlock tables;
|
|
flush tables with read lock;
|
|
unlock tables;
|
|
begin;
|
|
select * from t1;
|
|
a
|
|
1
|
|
10
|
|
show create database test;
|
|
Database Create Database
|
|
test CREATE DATABASE `test` /*!40100 DEFAULT CHARACTER SET latin1 */
|
|
drop table t1;
|