9 messages in com.mysql.lists.mysqlRe: replication blues
FromSent OnAttachments
Bogdan TARU12 Aug 2003 03:22 
Victoria Reznichenko12 Aug 2003 11:49 
Primaria Falticeni SDU13 Aug 2003 10:00 
Victoria Reznichenko15 Aug 2003 03:03 
Primaria Falticeni SDU18 Aug 2003 05:13 
Bogdan TARU09 Sep 2003 23:57 
Victoria Reznichenko17 Sep 2003 03:50 
Bogdan TARU18 Sep 2003 01:19 
Victoria Reznichenko18 Sep 2003 03:55 
Subject:Re: replication blues
From:Victoria Reznichenko (vict@ensita.net)
Date:09/17/2003 03:50:11 AM
List:com.mysql.lists.mysql

Bogdan TARU <bg@icomag.de> wrote:

So, back to the problems with auto_increment columns and replication problems. I have noticed this problem always occures when using INSERT SELECT syntax with an auto_increment key

simple example:

CREATE TABLE test1 (value INT); INSERT INTO test1 SET value=1; INSERT INTO test1 SET value=2; INSERT INTO test1 SET value=3;

CREATE TABLE test2 (id INT PRIMARY KEY AUTO_INCREMENT, value INT); INSERT INTO test2 SELECT NULL, value FROM test1;

test2 will have the keys 1,2,3 on the master and 3,4,5 on the slave.

Both the master and the slave are running 4.0.13, master is on freebsd 4.8 and slave on linux.

Thanks for report. Your bug the same as: http://bugs.mysql.com/bug.php?id=490

Upgrade MySQL server to the recent version.