# Testcase for Bug
# Testcase derived from sql-bench/test-insert

--source include/have_falcon.inc

set autocommit=1;

--disable_warnings
drop table if exists bench1;
--enable_warnings

create table bench1 (id int NOT NULL,id2 int NOT NULL,id3 int NOT NULL,
dummy1 char(30),primary key (id,id2),index ix_id3 (id3)) engine=Falcon;

insert into bench1 (id,id2,id3,dummy1) values (10863,10863,10863,'BCDEFGHIJK');
insert into bench1 (id,id2,id3,dummy1) values (10862,10862,10862,'BCDEFGHIJK');
insert into bench1 (id,id2,id3,dummy1) values (10000,10000,10000,'BCDEFGHIJK');

# Please do not focus on the fact that running many updates on one row
# looks artificial and differs to a real world application.
# The original "test-insert" benchmark runs on a table with ~ 300000 rows
# and performs updates on many different rows, but harvests the same wrong
# server response. The loop is only used to increase the probability that
# we see the bug, when we are running with such a limited amount of rows
# and different SQL statements.
let $num=100000;
--disable_abort_on_error
while ($num)
{
   update bench1 set id3=-10862 where id3=10862;
   if ($mysql_errno)
   {
      --echo Got an unexpected error after 100000 + 1 - $num UPDATEs
      --echo abort
      exit;
   }
   dec $num;
}
drop table bench1;