> Reading How AUTO_INCREMENT Handling Works in InnoDB[1] makes me
> wonder how is it possible to replicate AUTO_INCREMENTed value to slaves.
>
> According to the doc,
>
> "If you specify an AUTO_INCREMENT column for an InnoDB table, the
> table handle in the InnoDB data dictionary contains a special counter
> called the auto-increment counter that is used in assigning new values
> for the column. This counter is stored only in main memory, not on
> disk."
>
> Let's say there are two server, A and B. A replicates its data to B, the slave.
> A and B has a table that looks like(column 'id' is auto_increment field)
>
> id value
> 1 a
> 2 b
> 3 c
> 4 d
>
> If After "delete from table where id = 4" and restart mysqld on server B,
> "insert into table (value) values(e)" is executed on server A.


Why would you delete data from the slave?


>
> In this case, because A's internal counter is 4, table on A would be
> 1 a
> 2 b
> 3 c
> 5 e
>
> But B's would be different because restarting mysqld flushed InnoDB's
> internal counter.
> 1 a
> 2 b
> 3 c
> 4 e
>
> Is this correct?
> or MySQL is smart enough to handle this problem?
>
> Thanks.
>
> [1]http://dev.mysql.com/doc/refman/4.1/en/innodb-auto-increment-handling.html
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=m...hilip.pjkh.com
>
>