Bogdan TARU <[EMAIL PROTECTED]> 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.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Victoria Reznichenko
/ /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED]
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
<___/ www.mysql.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
