Hi, I have a master and a slave mysql server. On the master I write binlogs needed for replication. From time to time I have chronological auto_increment problems, here's a short explanation. - the table structure : | Field | Type | Null | Key | Default | Extra | +-------+-------------+------+-----+---------+----------------+ | id | int(11) | | PRI | NULL | auto_increment | | name | varchar(20) | | | | | ...
- when I update an the id field in this table (update tablename set id=....) and make an insert (insert into tablename set name=...) at the same time, it happens that first the update get performed and than the insert but with the old auto_increment values, here' a snipset from the binlog: --- # at 84043032 #051109 9:38:00 server id 4 log_pos 84043032 Query thread_id=27565652 exec_time=0 error_code=0 SET TIMESTAMP=1131525480; UPDATE tablename SET `id`=15183855 ... WHERE `id`=15159410; # at 84044721 #051109 9:38:00 server id 4 log_pos 84044026 Intvar SET INSERT_ID=15183827; # at 84044749 #051109 9:38:00 server id 4 log_pos 84044026 Query thread_id=27567781 exec_time=0 error_code=0 SET TIMESTAMP=1131525480; insert into tablename set name = ... --- So that the auto_increment value in this example after the queries 15183828, but it should be 15183856. Have anybody the same problems, it this a bug and is there a solution for this problem ? Thanks and Regards Andreas -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
