MySQL Bugs: #18052: Script inserts duplicate records

Bug #18052	Script inserts duplicate records
Submitted:	7 Mar 2006 22:26	Modified:	12 Sep 2006 9:59
Reporter:	Mike Smith	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S2 (Serious)
Version:	1.1.20	OS:	Windows (Windows XP Pro)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	Source Editors

Description:
While using executing a script from the Script tab, dupilcate records were created.

How to repeat:
1. Copied a script from the internet while completing a tuturial.
http://www.webdevelopersnotes.com/tutorials/sql/employee.dat
2. Pasted the script in to the script tab
3. Executed the script

Results
Duplicate records for all insert statements except the first one.

4. Tried with just one insert statement and it works fine.

5. Tried with mulitple insert statements again and it resulted in the same.

6. Tried with two insert statements and the first one executes properly, but the second statement is duplicated.

Thank you for a problem report. Please, describe the exact steps you perfromed. Each selection asnd click in GUI. Can you repeat with a simple set orf SQL statements that can be added to this bug report directly?

I just ran into this same bug.  I tried to run a sql script to populate a database table.

Duplicates were created for every record except the first sql statement.

This makes the script executor not very useful.  Any update on an expected date for a fix would be helpful.

Hi:

My env:
Query Browser:  1.1.19
MySQL:  mysql  Ver 14.7 Distrib 4.1.13a, for Win32 (ia32)
OS:  Windows XP Pro

Here are some simple steps to replicate this: 

1.  create test table:
CREATE TABLE `whatever`.`testit` (
  `id` INTEGER UNSIGNED NOT NULL AUTO_INCREMENT,
  `data` VARCHAR(45) NOT NULL DEFAULT '',
  PRIMARY KEY(`id`)
)
ENGINE = InnoDB;

2.  Create script that loads lots of data.  It doesnt seem to happen if you only insert a few rows:
insert into testit values (null,'row1');
insert into testit values (null,'row2');
insert into testit values (null,'row3');
insert into testit values (null,'row4');
insert into testit values (null,'row5');
insert into testit values (null,'row6');
insert into testit values (null,'row7');
insert into testit values (null,'row8');
insert into testit values (null,'row9');
insert into testit values (null,'row10');
insert into testit values (null,'row11');
...
...
...
insert into testit values (null,'row372');
insert into testit values (null,'row373');
insert into testit values (null,'row374');
insert into testit values (null,'row375');
insert into testit values (null,'row376');
insert into testit values (null,'row377');

3.  Execute the script.

4.  Read that data, back... dupes....

Please to be fixing...

Hi!

Just tested version 1.1.20 (on W2k SP4).
The Problem changed to the following:
After a set of insert-commands, now only exactly the second insert-command creates a duplicate entry in the table:

insert into test (field) values ("test1");
insert into test (field) values ("test2"); ==> creates this row double
insert into test (field) values ("test3");
insert into test (field) values ("test4");

A fix would be appreciated...

To reproduce:

1. Create the table:
CREATE TABLE  `foo` (
  `id` int(10) unsigned NOT NULL auto_increment,
  `name` varchar(10) NOT NULL default '',
  PRIMARY KEY  (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

2. Open a script tab in the MySQL Query Browser.

3. Add the following script:
insert into foo values(0,"a");
insert into foo values(0,"b");
insert into foo values(0,"c");
insert into foo values(0,"d");
insert into foo values(0,"e");

4. Press execute button
5. Select * from foo yeilds:
1, 'a'
2, 'b'
3, 'c'
4, 'd'
5, 'e'
6, 'e'

Confirming this bug using all kinds of insert statements. Please correct this as soon as possible, makes script function unusable!

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Please do not close the ticket. You have been provided a few examples from other users, so there is problem. I will provide more examples if you choose.

Thanks

Verified just as described in the comment posted at [21 Mar 17:22], with QB 1.1.20. In my case other values were duplicated, but the problem is really repeatable. It is a bug.

I am also finding that this happens with a the following:

1. Load Data local Infile 'f:\\stats\\SQLDb\\Raw\\2003\\CHM-0303_reqs.txt' into Table Requests Fields Terminated by ',' optionally enclosed by '"' lines terminated by '\r\n';

2. Load Data local Infile 'f:\\stats\\SQLDb\\Raw\\2003\\CHM-0303_sets.txt' into Table Sets Fields Terminated by ',' optionally enclosed by '"' lines terminated by '\r\n';

3. Load Data local Infile 'f:\\stats\\SQLDb\\Raw\\2003\\CHM-0303_tests.txt' into Table tests Fields Terminated by ',' optionally enclosed by '"' lines terminated by '\r\n';'

I split the lines up to show the 3 statements. The 3rd Load gets run twice by the query browser.

Query Browser: version 1.1.20
Server version: 4.1.18(intial); 5.0.18(testing)

Additional observations:

Statements used to reproduce:
--------------------
create table temp_a ( id integer unsigned not null auto_increment, mydata integer unsigned not null, PRIMARY KEY (`id`) );
insert into temp_a ( id, mydata ) values (1, 1), (2, 2);
UPDATE temp_a SET mydata = ( mydata + 1 ) WHERE id = 1;
UPDATE temp_a SET mydata = ( mydata + 1 ) WHERE id = 2;
--------------------

Observations:

The duplicate execution of rows only seems to happen when the statements above are initially pasted into the query browser.  When it's pasted then executed without any other modifications being done inside the script tab window, it will cause some of the queries to be executed multiple times.  The first and last queries (or lines, if you have a -- comment on the first line ) in the list seem to only execute a single time.  If I type into the script tab and enter a newline before the first query or after the first query ( after the ; ), everything appears to execute correctly from that point on inside of that script tab. (Although deleting the entire contents of the script tab and re-entering the statements will cause the duplicate effect again )  The problem also only seems to exist when more then 1-2 queries/lines are executed.

Duplicate of Bug #16607