2006-09-21 13:19:52 +02:00
|
|
|
#
|
|
|
|
# Setup
|
|
|
|
#
|
2003-02-07 14:47:24 +01:00
|
|
|
stop slave;
|
2003-01-28 08:17:10 +01:00
|
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
|
|
|
reset master;
|
|
|
|
reset slave;
|
|
|
|
drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9;
|
2003-02-07 14:47:24 +01:00
|
|
|
start slave;
|
2006-09-21 13:19:52 +02:00
|
|
|
use test;
|
|
|
|
drop table if exists t1, t2, t3;
|
|
|
|
#
|
|
|
|
# See if queries that use both auto_increment and LAST_INSERT_ID()
|
|
|
|
# are replicated well
|
|
|
|
#
|
|
|
|
# We also check how the foreign_key_check variable is replicated
|
|
|
|
#
|
2003-01-28 08:17:10 +01:00
|
|
|
create table t1(a int auto_increment, key(a));
|
|
|
|
create table t2(b int auto_increment, c int, key(b));
|
|
|
|
insert into t1 values (1),(2),(3);
|
|
|
|
insert into t1 values (null);
|
|
|
|
insert into t2 values (null,last_insert_id());
|
|
|
|
select * from t1;
|
2003-01-28 05:48:26 +01:00
|
|
|
a
|
|
|
|
1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
2003-01-28 08:17:10 +01:00
|
|
|
select * from t2;
|
2003-01-28 05:48:26 +01:00
|
|
|
b c
|
|
|
|
1 4
|
2003-01-28 08:17:10 +01:00
|
|
|
drop table t1;
|
|
|
|
drop table t2;
|
2003-12-10 05:31:42 +01:00
|
|
|
create table t1(a int auto_increment, key(a)) engine=innodb;
|
|
|
|
create table t2(b int auto_increment, c int, key(b), foreign key(b) references t1(a)) engine=innodb;
|
2003-05-26 14:08:17 +02:00
|
|
|
SET FOREIGN_KEY_CHECKS=0;
|
2003-01-28 08:17:10 +01:00
|
|
|
insert into t1 values (10);
|
|
|
|
insert into t1 values (null),(null),(null);
|
|
|
|
insert into t2 values (5,0);
|
|
|
|
insert into t2 values (null,last_insert_id());
|
2003-05-26 14:08:17 +02:00
|
|
|
SET FOREIGN_KEY_CHECKS=1;
|
2003-01-28 08:17:10 +01:00
|
|
|
select * from t1;
|
2003-01-28 05:48:26 +01:00
|
|
|
a
|
|
|
|
10
|
|
|
|
11
|
|
|
|
12
|
|
|
|
13
|
2003-01-28 08:17:10 +01:00
|
|
|
select * from t2;
|
2003-01-28 05:48:26 +01:00
|
|
|
b c
|
|
|
|
5 0
|
|
|
|
6 11
|
2006-09-21 13:19:52 +02:00
|
|
|
#
|
|
|
|
# check if INSERT SELECT in auto_increment is well replicated (bug #490)
|
|
|
|
#
|
2003-01-28 08:17:10 +01:00
|
|
|
drop table t2;
|
2004-02-02 00:41:35 +01:00
|
|
|
drop table t1;
|
2003-05-24 16:43:53 +02:00
|
|
|
create table t1(a int auto_increment, key(a));
|
|
|
|
create table t2(b int auto_increment, c int, key(b));
|
|
|
|
insert into t1 values (10);
|
|
|
|
insert into t1 values (null),(null),(null);
|
|
|
|
insert into t2 values (5,0);
|
|
|
|
insert into t2 (c) select * from t1;
|
|
|
|
select * from t2;
|
|
|
|
b c
|
|
|
|
5 0
|
|
|
|
6 10
|
|
|
|
7 11
|
|
|
|
8 12
|
|
|
|
9 13
|
|
|
|
select * from t1;
|
|
|
|
a
|
|
|
|
10
|
|
|
|
11
|
|
|
|
12
|
|
|
|
13
|
|
|
|
select * from t2;
|
|
|
|
b c
|
|
|
|
5 0
|
|
|
|
6 10
|
|
|
|
7 11
|
|
|
|
8 12
|
|
|
|
9 13
|
|
|
|
drop table t1;
|
|
|
|
drop table t2;
|
2006-09-21 13:19:52 +02:00
|
|
|
#
|
|
|
|
# Bug#8412: Error codes reported in binary log for CHARACTER SET,
|
|
|
|
# FOREIGN_KEY_CHECKS
|
|
|
|
#
|
2005-02-14 18:39:33 +01:00
|
|
|
SET TIMESTAMP=1000000000;
|
|
|
|
CREATE TABLE t1 ( a INT UNIQUE );
|
|
|
|
SET FOREIGN_KEY_CHECKS=0;
|
|
|
|
INSERT INTO t1 VALUES (1),(1);
|
2005-02-24 17:25:06 +01:00
|
|
|
ERROR 23000: Duplicate entry '1' for key 1
|
2006-09-21 13:19:52 +02:00
|
|
|
#
|
|
|
|
# Bug#14553: NULL in WHERE resets LAST_INSERT_ID
|
|
|
|
#
|
2006-07-10 15:27:03 +02:00
|
|
|
drop table t1;
|
|
|
|
create table t1(a int auto_increment, key(a));
|
|
|
|
create table t2(a int);
|
|
|
|
insert into t1 (a) values (null);
|
|
|
|
insert into t2 (a) select a from t1 where a is null;
|
|
|
|
insert into t2 (a) select a from t1 where a is null;
|
|
|
|
select * from t2;
|
|
|
|
a
|
|
|
|
1
|
|
|
|
select * from t2;
|
|
|
|
a
|
|
|
|
1
|
|
|
|
drop table t1;
|
|
|
|
drop table t2;
|
BUG#21726: Incorrect result with multiple invocations of LAST_INSERT_ID.
Note: bug#21726 does not directly apply to 4.1, as it doesn't have stored
procedures. However, 4.1 had some bugs that were fixed in 5.0 by the
patch for bug#21726, and this patch is a backport of those fixes.
Namely, in 4.1 it fixes:
- LAST_INSERT_ID(expr) didn't return value of expr (4.1 specific).
- LAST_INSERT_ID() could return the value generated by current
statement if the call happens after the generation, like in
CREATE TABLE t1 (i INT AUTO_INCREMENT PRIMARY KEY, j INT);
INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
- Redundant binary log LAST_INSERT_ID_EVENTs could be generated.
mysql-test/r/rpl_insert_id.result:
Add result for bug#21726: Incorrect result with multiple invocations
of LAST_INSERT_ID.
mysql-test/t/rpl_insert_id.test:
Add test case for bug#21726: Incorrect result with multiple invocations
of LAST_INSERT_ID.
sql/item_func.cc:
Add implementation of Item_func_last_insert_id::fix_fields(), where we
set THD::last_insert_id_used when statement calls LAST_INSERT_ID().
In Item_func_last_insert_id::val_int(), return THD::current_insert_id
if called like LAST_INSERT_ID(), otherwise return value of argument if
called like LAST_INSERT_ID(expr).
sql/item_func.h:
Add declaration of Item_func_last_insert_id::fix_fields().
sql/log_event.cc:
Do not set THD::last_insert_id_used on LAST_INSERT_ID_EVENT. Though we
know the statement will call LAST_INSERT_ID(), it wasn't called yet.
sql/set_var.cc:
In sys_var_last_insert_id::value_ptr(), set THD::last_insert_id_used,
and return THD::current_insert_id for @@LAST_INSERT_ID.
sql/sql_class.h:
Update comments.
Remove THD::insert_id(), as it has lost its purpose now.
sql/sql_insert.cc:
Now it is OK to read THD::last_insert_id directly.
sql/sql_load.cc:
Now it is OK to read THD::last_insert_id directly.
sql/sql_parse.cc:
In mysql_execute_command(), remember THD::last_insert_id (first
generated value of the previous statement) in THD::current_insert_id,
which then will be returned for LAST_INSERT_ID() and @@LAST_INSERT_ID.
sql/sql_select.cc:
If "IS NULL" is replaced with "= <LAST_INSERT_ID>", use right value,
which is THD::current_insert_id, and also set THD::last_insert_id_used
to issue binary log LAST_INSERT_ID_EVENT.
sql/sql_update.cc:
Now it is OK to read THD::last_insert_id directly.
tests/mysql_client_test.c:
Add test case for bug#21726: Incorrect result with multiple invocations
of LAST_INSERT_ID.
2006-10-06 11:34:07 +02:00
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
i INT NOT NULL AUTO_INCREMENT PRIMARY KEY,
|
|
|
|
j INT DEFAULT 0
|
|
|
|
);
|
|
|
|
INSERT INTO t1 VALUES (NULL, -1);
|
|
|
|
INSERT INTO t1 VALUES (NULL, LAST_INSERT_ID()), (NULL, LAST_INSERT_ID(5)),
|
|
|
|
(NULL, @@LAST_INSERT_ID);
|
|
|
|
INSERT INTO t1 VALUES (NULL, 0), (NULL, LAST_INSERT_ID());
|
|
|
|
UPDATE t1 SET j= -1 WHERE i IS NULL;
|
|
|
|
SELECT * FROM t1;
|
|
|
|
i j
|
|
|
|
1 -1
|
|
|
|
2 1
|
|
|
|
3 5
|
|
|
|
4 1
|
|
|
|
5 -1
|
|
|
|
6 2
|
|
|
|
SELECT * FROM t1;
|
|
|
|
i j
|
|
|
|
1 -1
|
|
|
|
2 1
|
|
|
|
3 5
|
|
|
|
4 1
|
|
|
|
5 -1
|
|
|
|
6 2
|
|
|
|
DROP TABLE t1;
|
2006-09-21 13:19:52 +02:00
|
|
|
#
|
|
|
|
# End of 4.1 tests
|
|
|
|
#
|