2000-12-28 02:56:38 +01:00
|
|
|
#
|
|
|
|
|
# Test of refering to old values
|
|
|
|
|
#
|
|
|
|
|
|
2003-01-06 00:48:59 +01:00
|
|
|
--disable_warnings
|
2004-10-29 18:26:52 +02:00
|
|
|
drop table if exists t1,t2,t3;
|
2003-01-06 00:48:59 +01:00
|
|
|
--enable_warnings
|
|
|
|
|
|
2000-12-28 02:56:38 +01:00
|
|
|
create table t1 (a int not null);
|
|
|
|
|
insert into t1 values (1);
|
|
|
|
|
insert into t1 values (a+2);
|
|
|
|
|
insert into t1 values (a+3);
|
|
|
|
|
insert into t1 values (4),(a+5);
|
|
|
|
|
select * from t1;
|
|
|
|
|
drop table t1;
|
2001-06-25 10:35:22 +02:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Test of duplicate key values with packed keys
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
create table t1 (id int not null auto_increment primary key, username varchar(32) not null, unique (username));
|
|
|
|
|
insert into t1 values (0,"mysql");
|
|
|
|
|
insert into t1 values (0,"mysql ab");
|
|
|
|
|
insert into t1 values (0,"mysql a");
|
|
|
|
|
insert into t1 values (0,"r1manic");
|
|
|
|
|
insert into t1 values (0,"r1man");
|
|
|
|
|
drop table t1;
|
2002-07-25 00:00:56 +02:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Test insert syntax
|
|
|
|
|
#
|
|
|
|
|
|
2002-08-08 02:12:02 +02:00
|
|
|
create table t1 (a int not null auto_increment, primary key (a), t timestamp, c char(10) default "hello", i int);
|
|
|
|
|
insert into t1 values (default,default,default,default), (default,default,default,default), (4,0,"a",5),(default,default,default,default);
|
|
|
|
|
select a,t>0,c,i from t1;
|
2002-07-25 00:00:56 +02:00
|
|
|
truncate table t1;
|
|
|
|
|
insert into t1 set a=default,t=default,c=default;
|
2002-08-08 02:12:02 +02:00
|
|
|
insert into t1 set a=default,t=default,c=default,i=default;
|
|
|
|
|
insert into t1 set a=4,t=0,c="a",i=5;
|
|
|
|
|
insert into t1 set a=5,t=0,c="a",i=null;
|
|
|
|
|
insert into t1 set a=default,t=default,c=default,i=default;
|
|
|
|
|
select a,t>0,c,i from t1;
|
2002-07-25 00:00:56 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
2002-09-18 20:04:49 +02:00
|
|
|
#
|
|
|
|
|
# Test problem with bulk insert and auto_increment on second part keys
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
create table t1 (sid char(20), id int(2) NOT NULL auto_increment, key(sid, id));
|
|
|
|
|
insert into t1 values ('skr',NULL),('skr',NULL),('test',NULL);
|
|
|
|
|
select * from t1;
|
2002-12-07 22:40:20 +01:00
|
|
|
insert into t1 values ('rts',NULL),('rts',NULL),('test',NULL);
|
|
|
|
|
select * from t1;
|
2002-09-18 20:04:49 +02:00
|
|
|
drop table t1;
|
|
|
|
|
|
2003-06-24 07:53:21 +02:00
|
|
|
#
|
|
|
|
|
#Test of behaviour with INSERT VALUES (NULL)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
create table t1 (id int NOT NULL DEFAULT 8);
|
|
|
|
|
-- error 1048
|
|
|
|
|
insert into t1 values(NULL);
|
|
|
|
|
insert into t1 values (1), (NULL), (2);
|
|
|
|
|
select * from t1;
|
|
|
|
|
drop table t1;
|
|
|
|
|
|
2003-09-29 11:31:35 +02:00
|
|
|
#
|
|
|
|
|
# Test if insert ... select distinct
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
create table t1 (email varchar(50));
|
|
|
|
|
insert into t1 values ('sasha@mysql.com'),('monty@mysql.com'),('foo@hotmail.com'),('foo@aol.com'),('bar@aol.com');
|
|
|
|
|
create table t2(id int not null auto_increment primary key, t2 varchar(50), unique(t2));
|
2003-12-14 05:39:52 +01:00
|
|
|
insert delayed into t2 (t2) select distinct substring(email, locate('@', email)+1) from t1;
|
2003-09-29 11:31:35 +02:00
|
|
|
select * from t2;
|
|
|
|
|
drop table t1,t2;
|
|
|
|
|
|
2002-07-25 00:00:56 +02:00
|
|
|
#
|
|
|
|
|
# Test of mysqld crash with fully qualified column names
|
|
|
|
|
#
|
|
|
|
|
|
2003-01-06 00:48:59 +01:00
|
|
|
--disable_warnings
|
2003-10-08 11:01:58 +02:00
|
|
|
drop database if exists mysqltest;
|
2003-01-06 00:48:59 +01:00
|
|
|
--enable_warnings
|
2003-10-08 11:01:58 +02:00
|
|
|
create database mysqltest;
|
|
|
|
|
use mysqltest;
|
2002-07-25 00:00:56 +02:00
|
|
|
create table t1 (c int);
|
2003-10-08 11:01:58 +02:00
|
|
|
insert into mysqltest.t1 set mysqltest.t1.c = '1';
|
|
|
|
|
drop database mysqltest;
|
2004-10-29 18:26:52 +02:00
|
|
|
use test;
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Test of wrong values for float data (bug #2082)
|
2004-03-06 00:00:21 +01:00
|
|
|
#
|
|
|
|
|
|
2004-10-26 18:30:01 +02:00
|
|
|
# PS gives sligthly different numbers for max-float/max-double
|
|
|
|
|
--disable_ps_protocol
|
2004-03-17 23:09:13 +01:00
|
|
|
create table t1(number int auto_increment primary key, original_value varchar(50), f_double double, f_float float, f_double_7_2 double(7,2), f_float_4_3 float (4,3), f_double_u double unsigned, f_float_u float unsigned, f_double_15_1_u double(15,1) unsigned, f_float_3_1_u float (3,1) unsigned);
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= "aa";
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= "1aa";
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= "aa1";
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= "1e+1111111111a";
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= "-1e+1111111111a";
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
2004-10-02 21:20:08 +02:00
|
|
|
--error 1367
|
2004-03-04 18:08:14 +01:00
|
|
|
set @value= 1e+1111111111;
|
2004-10-02 21:20:08 +02:00
|
|
|
--error 1367
|
2004-03-04 18:08:14 +01:00
|
|
|
set @value= -1e+1111111111;
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
set @value= 1e+111;
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= -1e+111;
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= 1;
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
set @value= -1;
|
|
|
|
|
insert into t1 values(null,@value,@value,@value,@value,@value,@value,@value,@value,@value);
|
2004-03-17 23:09:13 +01:00
|
|
|
--query_vertical select * from t1 where number =last_insert_id()
|
2004-03-04 18:08:14 +01:00
|
|
|
|
|
|
|
|
drop table t1;
|
2004-10-26 18:30:01 +02:00
|
|
|
--enable_ps_protocol
|
2004-10-29 18:26:52 +02:00
|
|
|
|
2005-07-28 02:22:47 +02:00
|
|
|
# End of 4.1 tests
|
2005-07-28 16:09:54 +02:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Test automatic result buffering with INSERT INTO t1 ... SELECT ... FROM t1
|
|
|
|
|
#
|
|
|
|
|
|
2003-01-28 17:55:52 +01:00
|
|
|
create table t1(id1 int not null auto_increment primary key, t char(12));
|
|
|
|
|
create table t2(id2 int not null, t char(12));
|
|
|
|
|
create table t3(id3 int not null, t char(12), index(id3));
|
|
|
|
|
disable_query_log;
|
|
|
|
|
let $1 = 100;
|
|
|
|
|
while ($1)
|
|
|
|
|
{
|
|
|
|
|
let $2 = 5;
|
|
|
|
|
eval insert into t1(t) values ('$1');
|
|
|
|
|
while ($2)
|
|
|
|
|
{
|
|
|
|
|
eval insert into t2(id2,t) values ($1,'$2');
|
|
|
|
|
let $3 = 10;
|
|
|
|
|
while ($3)
|
|
|
|
|
{
|
|
|
|
|
eval insert into t3(id3,t) values ($1,'$2');
|
|
|
|
|
dec $3;
|
|
|
|
|
}
|
|
|
|
|
dec $2;
|
|
|
|
|
}
|
|
|
|
|
dec $1;
|
|
|
|
|
}
|
|
|
|
|
enable_query_log;
|
|
|
|
|
select count(*) from t2;
|
|
|
|
|
insert into t2 select t1.* from t1, t2 t, t3 where t1.id1 = t.id2 and t.id2 = t3.id3;
|
|
|
|
|
select count(*) from t2;
|
2004-10-29 18:26:52 +02:00
|
|
|
drop table t1,t2,t3;
|
2006-04-04 23:09:07 +02:00
|
|
|
|
2006-06-16 18:21:25 +02:00
|
|
|
#
|
|
|
|
|
# Test for values returned by ROW_COUNT() function
|
|
|
|
|
# (and thus for values returned by mysql_affected_rows())
|
|
|
|
|
# for various forms of INSERT
|
|
|
|
|
#
|
|
|
|
|
create table t1 (id int primary key, data int);
|
|
|
|
|
insert into t1 values (1, 1), (2, 2), (3, 3);
|
|
|
|
|
select row_count();
|
|
|
|
|
insert ignore into t1 values (1, 1);
|
|
|
|
|
select row_count();
|
|
|
|
|
# Reports that 2 rows are affected (1 deleted + 1 inserted)
|
|
|
|
|
replace into t1 values (1, 11);
|
|
|
|
|
select row_count();
|
|
|
|
|
replace into t1 values (4, 4);
|
|
|
|
|
select row_count();
|
|
|
|
|
# Reports that 2 rows are affected. This conforms to documentation.
|
|
|
|
|
# (Useful for differentiating inserts from updates).
|
|
|
|
|
insert into t1 values (2, 2) on duplicate key update data= data + 10;
|
|
|
|
|
select row_count();
|
|
|
|
|
insert into t1 values (5, 5) on duplicate key update data= data + 10;
|
|
|
|
|
select row_count();
|
|
|
|
|
drop table t1;
|
2007-01-22 13:14:38 +01:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bug#25123: ON DUPLICATE KEY clause allows fields not from the insert table
|
|
|
|
|
#
|
|
|
|
|
create table t1 (f1 int unique, f2 int);
|
|
|
|
|
create table t2 (f3 int, f4 int);
|
|
|
|
|
create view v1 as select * from t1, t2 where f1= f3;
|
|
|
|
|
insert into t1 values (1,11), (2,22);
|
|
|
|
|
insert into t2 values (1,12), (2,24);
|
|
|
|
|
--error 1393
|
|
|
|
|
insert into v1 (f1) values (3) on duplicate key update f3= f3 + 10;
|
|
|
|
|
insert into v1 (f1) values (3) on duplicate key update f1= f3 + 10;
|
|
|
|
|
select * from t1;
|
|
|
|
|
insert into v1 (f1) values (3) on duplicate key update f1= f3 + 10;
|
|
|
|
|
select * from t1;
|
|
|
|
|
drop view v1;
|
|
|
|
|
drop table t1,t2;
|
|
|
|
|
|
A fix and a test case for
Bug#21483 "Server abort or deadlock on INSERT DELAYED with another
implicit insert"
Also fixes and adds test cases for bugs:
20497 "Trigger with INSERT DELAYED causes Error 1165"
21714 "Wrong NEW.value and server abort on INSERT DELAYED to a
table with a trigger".
Post-review fixes.
Problem:
In MySQL INSERT DELAYED is a way to pipe all inserts into a
given table through a dedicated thread. This is necessary for
simplistic storage engines like MyISAM, which do not have internal
concurrency control or threading and thus can not
achieve efficient INSERT throughput without support from SQL layer.
DELAYED INSERT works as follows:
For every distinct table, which can accept DELAYED inserts and has
pending data to insert, a dedicated thread is created to write data
to disk. All user connection threads that attempt to
delayed-insert into this table interact with the dedicated thread in
producer/consumer fashion: all records to-be inserted are pushed
into a queue of the dedicated thread, which fetches the records and
writes them.
In this design, client connection threads never open or lock
the delayed insert table.
This functionality was introduced in version 3.23 and does not take
into account existence of triggers, views, or pre-locking.
E.g. if INSERT DELAYED is called from a stored function, which,
in turn, is called from another stored function that uses the delayed
table, a deadlock can occur, because delayed locking by-passes
pre-locking. Besides:
* the delayed thread works directly with the subject table through
the storage engine API and does not invoke triggers
* even if it was patched to invoke triggers, if triggers,
in turn, used other tables, the delayed thread would
have to open and lock involved tables (use pre-locking).
* even if it was patched to use pre-locking, without deadlock
detection the delayed thread could easily lock out user
connection threads in case when the same table is used both
in a trigger and on the right side of the insert query:
the delayed thread would not release locks until all inserts
are complete, and user connection can not complete inserts
without having locks on the tables used on the right side of the
query.
Solution:
These considerations suggest two general alternatives for the
future of INSERT DELAYED:
* it is considered a full-fledged alternative to normal INSERT
* it is regarded as an optimisation that is only relevant
for simplistic engines.
Since we missed our chance to provide complete support of new
features when 5.0 was in development, the first alternative
currently renders infeasible.
However, even the second alternative, which is to detect
new features and convert DELAYED insert into a normal insert,
is not easy to implement.
The catch-22 is that we don't know if the subject table has triggers
or is a view before we open it, and we only open it in the
delayed thread. We don't know if the query involves pre-locking
until we have opened all tables, and we always first create
the delayed thread, and only then open the remaining tables.
This patch detects the problematic scenarios and converts
DELAYED INSERT to a normal INSERT using the following approach:
* if the statement is executed under pre-locking (e.g. from
within a stored function or trigger) or the right
side may require pre-locking, we detect the situation
before creating a delayed insert thread and convert the statement
to a conventional INSERT.
* if the subject table is a view or has triggers, we shutdown
the delayed thread and convert the statement to a conventional
INSERT.
2007-05-16 07:51:05 +02:00
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# BUG#21483: Server abort or deadlock on INSERT DELAYED with another
|
|
|
|
|
# implicit insert
|
|
|
|
|
#
|
|
|
|
|
# The solution is to downgrade INSERT DELAYED to normal INSERT if the
|
|
|
|
|
# statement uses functions and access tables or triggers, or is called
|
|
|
|
|
# from a function or a trigger.
|
|
|
|
|
#
|
|
|
|
|
--disable_warnings
|
|
|
|
|
DROP TABLE IF EXISTS t1;
|
|
|
|
|
DROP FUNCTION IF EXISTS f1;
|
|
|
|
|
DROP FUNCTION IF EXISTS f2;
|
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
delimiter |;
|
|
|
|
|
CREATE FUNCTION f1() RETURNS INT
|
|
|
|
|
BEGIN
|
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
|
RETURN 1;
|
|
|
|
|
END |
|
|
|
|
|
CREATE FUNCTION f2() RETURNS INT
|
|
|
|
|
BEGIN
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (2);
|
|
|
|
|
RETURN 1;
|
|
|
|
|
END |
|
|
|
|
|
delimiter ;|
|
|
|
|
|
|
|
|
|
|
SELECT f1();
|
|
|
|
|
SELECT f2();
|
|
|
|
|
INSERT INTO t1 VALUES (3);
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (4);
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT INTO t1 VALUES (f1());
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (f1());
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT INTO t1 VALUES (f2());
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (f2());
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
|
INSERT INTO t1 VALUES (NEW.i);
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
|
|
|
|
|
|
--error ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (1);
|
|
|
|
|
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
|
|
DROP FUNCTION f2;
|
|
|
|
|
DROP FUNCTION f1;
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# BUG#20497: Trigger with INSERT DELAYED causes Error 1165
|
|
|
|
|
#
|
|
|
|
|
# Fixed by the patch for Bug#21483
|
|
|
|
|
#
|
|
|
|
|
--disable_warnings
|
|
|
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
CREATE TABLE t2 (i INT);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
|
INSERT DELAYED INTO t2 VALUES (NEW.i);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_bu BEFORE UPDATE ON t1 FOR EACH ROW
|
|
|
|
|
INSERT DELAYED INTO t2 VALUES (NEW.i);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_bd BEFORE DELETE ON t1 FOR EACH ROW
|
|
|
|
|
INSERT DELAYED INTO t2 VALUES (OLD.i);
|
|
|
|
|
|
|
|
|
|
INSERT INTO t1 VALUES (1);
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (2);
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
UPDATE t1 SET i = 3 WHERE i = 1;
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
DELETE FROM t1 WHERE i = 3;
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# BUG#21714: Wrong NEW.value and server abort on INSERT DELAYED to a
|
|
|
|
|
# table with a trigger
|
|
|
|
|
#
|
|
|
|
|
# Fixed by the patch for Bug#21483
|
|
|
|
|
#
|
|
|
|
|
--disable_warnings
|
|
|
|
|
DROP TABLE IF EXISTS t1, t2;
|
|
|
|
|
--enable_warnings
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
CREATE TRIGGER t1_bi BEFORE INSERT ON t1 FOR EACH ROW
|
|
|
|
|
SET @a= NEW.i;
|
|
|
|
|
|
|
|
|
|
SET @a= 0;
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (1);
|
|
|
|
|
SELECT @a;
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (2);
|
|
|
|
|
SELECT @a;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (i INT);
|
|
|
|
|
CREATE TABLE t2 (i INT);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_ai AFTER INSERT ON t1 FOR EACH ROW
|
|
|
|
|
INSERT INTO t2 VALUES (NEW.i);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_au AFTER UPDATE ON t1 FOR EACH ROW
|
|
|
|
|
INSERT DELAYED INTO t2 VALUES (NEW.i);
|
|
|
|
|
|
|
|
|
|
CREATE TRIGGER t1_ad AFTER DELETE ON t1 FOR EACH ROW
|
|
|
|
|
INSERT DELAYED INTO t2 VALUES (OLD.i);
|
|
|
|
|
|
|
|
|
|
INSERT DELAYED INTO t1 VALUES (1);
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
UPDATE t1 SET i = 2 WHERE i = 1;
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
DELETE FROM t1 WHERE i = 2;
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
|
2007-12-01 08:05:59 +01:00
|
|
|
#
|
|
|
|
|
# Bug #26788: mysqld (debug) aborts when inserting specific numbers into char
|
|
|
|
|
# fields
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
|
a char(20) NOT NULL,
|
|
|
|
|
b char(7) DEFAULT NULL,
|
|
|
|
|
c char(4) DEFAULT NULL
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (9.999999e+0, 9.999999e+0, 9.999e+0);
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (1.225e-05, 1.225e-05, 1.225e-05);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e-04, 1.225e-04);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e-01, 1.225e-01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225877e-01, 1.225877e-01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+01, 1.225e+01);
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (1.225e+01, 1.225e+01, 1.225e+01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+05, 1.225e+05);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+10, 1.225e+10);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+15, 1.225e+15);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (5000000e+0, 5000000e+0);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e+78, 1.25e+78);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e-94, 1.25e-94);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e+203, 1.25e+203);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e-175, 1.25e-175);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.225e+0, 1.225e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.37e+0, 1.37e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-1.37e+0, -1.37e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.87e-3, 1.87e-3);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-1.87e-2, -1.87e-2);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (5000e+0, 5000e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-5000e+0, -5000e+0);
|
2007-12-01 13:25:24 +01:00
|
|
|
# Expected results are "12.2" and "1.2e+78", but Windows returns "12.3" and
|
|
|
|
|
# "1.3e+78" due to different rounding rules
|
|
|
|
|
--replace_result 12.3 12.2 1.3e+78 1.2e+78
|
2007-12-01 08:05:59 +01:00
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (
|
|
|
|
|
a char(20) NOT NULL,
|
|
|
|
|
b char(7) DEFAULT NULL,
|
|
|
|
|
c char(5)
|
|
|
|
|
);
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (9.999999e+0, 9.999999e+0, 9.999e+0);
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (1.225e-05, 1.225e-05, 1.225e-05);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e-04, 1.225e-04);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e-01, 1.225e-01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225877e-01, 1.225877e-01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+01, 1.225e+01);
|
|
|
|
|
INSERT INTO t1(a,b,c) VALUES (1.225e+01, 1.225e+01, 1.225e+01);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+05, 1.225e+05);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+10, 1.225e+10);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.225e+15, 1.225e+15);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (5000000e+0, 5000000e+0);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e+78, 1.25e+78);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e-94, 1.25e-94);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e+203, 1.25e+203);
|
|
|
|
|
INSERT INTO t1(a,b) VALUES (1.25e-175, 1.25e-175);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.225e+0, 1.225e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.37e+0, 1.37e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-1.37e+0, -1.37e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (1.87e-3, 1.87e-3);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-1.87e-2, -1.87e-2);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (5000e+0, 5000e+0);
|
|
|
|
|
INSERT INTO t1(a,c) VALUES (-5000e+0, -5000e+0);
|
|
|
|
|
|
2007-12-02 11:49:12 +01:00
|
|
|
# Expected results are "12.2" and "1.2e+78", but Windows returns "12.3" and
|
|
|
|
|
# "1.3e+78" due to different rounding rules
|
|
|
|
|
--replace_result 12.3 12.2 1.3e+78 1.2e+78
|
2007-12-01 08:05:59 +01:00
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1;
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# Bug #31152: assertion in Field_str::store(double)
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t (a CHAR(10),b INT);
|
|
|
|
|
INSERT INTO t VALUES (),(),();
|
|
|
|
|
INSERT INTO t(a) SELECT rand() FROM t;
|
|
|
|
|
DROP TABLE t;
|
|
|
|
|
|
2007-10-15 08:34:34 +02:00
|
|
|
#
|
|
|
|
|
# Bug #30453: String not cast to int correctly
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t1 (c1 INT NOT NULL);
|
|
|
|
|
INSERT INTO t1 VALUES(4188.32999999999992724042385816574096679687500),
|
|
|
|
|
('4188.32999999999992724042385816574096679687500'), (4188);
|
|
|
|
|
SELECT * FROM t1;
|
|
|
|
|
|
|
|
|
|
CREATE TABLE t2 (c1 BIGINT);
|
|
|
|
|
INSERT INTO t2 VALUES('15449237462.0000000000');
|
|
|
|
|
SELECT * FROM t2;
|
|
|
|
|
|
|
|
|
|
DROP TABLE t1, t2;
|
|
|
|
|
|
A fix and a test case for
Bug#21483 "Server abort or deadlock on INSERT DELAYED with another
implicit insert"
Also fixes and adds test cases for bugs:
20497 "Trigger with INSERT DELAYED causes Error 1165"
21714 "Wrong NEW.value and server abort on INSERT DELAYED to a
table with a trigger".
Post-review fixes.
Problem:
In MySQL INSERT DELAYED is a way to pipe all inserts into a
given table through a dedicated thread. This is necessary for
simplistic storage engines like MyISAM, which do not have internal
concurrency control or threading and thus can not
achieve efficient INSERT throughput without support from SQL layer.
DELAYED INSERT works as follows:
For every distinct table, which can accept DELAYED inserts and has
pending data to insert, a dedicated thread is created to write data
to disk. All user connection threads that attempt to
delayed-insert into this table interact with the dedicated thread in
producer/consumer fashion: all records to-be inserted are pushed
into a queue of the dedicated thread, which fetches the records and
writes them.
In this design, client connection threads never open or lock
the delayed insert table.
This functionality was introduced in version 3.23 and does not take
into account existence of triggers, views, or pre-locking.
E.g. if INSERT DELAYED is called from a stored function, which,
in turn, is called from another stored function that uses the delayed
table, a deadlock can occur, because delayed locking by-passes
pre-locking. Besides:
* the delayed thread works directly with the subject table through
the storage engine API and does not invoke triggers
* even if it was patched to invoke triggers, if triggers,
in turn, used other tables, the delayed thread would
have to open and lock involved tables (use pre-locking).
* even if it was patched to use pre-locking, without deadlock
detection the delayed thread could easily lock out user
connection threads in case when the same table is used both
in a trigger and on the right side of the insert query:
the delayed thread would not release locks until all inserts
are complete, and user connection can not complete inserts
without having locks on the tables used on the right side of the
query.
Solution:
These considerations suggest two general alternatives for the
future of INSERT DELAYED:
* it is considered a full-fledged alternative to normal INSERT
* it is regarded as an optimisation that is only relevant
for simplistic engines.
Since we missed our chance to provide complete support of new
features when 5.0 was in development, the first alternative
currently renders infeasible.
However, even the second alternative, which is to detect
new features and convert DELAYED insert into a normal insert,
is not easy to implement.
The catch-22 is that we don't know if the subject table has triggers
or is a view before we open it, and we only open it in the
delayed thread. We don't know if the query involves pre-locking
until we have opened all tables, and we always first create
the delayed thread, and only then open the remaining tables.
This patch detects the problematic scenarios and converts
DELAYED INSERT to a normal INSERT using the following approach:
* if the statement is executed under pre-locking (e.g. from
within a stored function or trigger) or the right
side may require pre-locking, we detect the situation
before creating a delayed insert thread and convert the statement
to a conventional INSERT.
* if the subject table is a view or has triggers, we shutdown
the delayed thread and convert the statement to a conventional
INSERT.
2007-05-16 07:51:05 +02:00
|
|
|
--echo End of 5.0 tests.
|
|
|
|
|
|