Bug #48900 | Autoincrement fault on temporary table | ||
---|---|---|---|
Submitted: | 19 Nov 2009 11:59 | Modified: | 21 Nov 2009 15:45 |
Reporter: | KREME LANDRY KOSSONOU | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | MySQL 5.1.40-Commuity via TCP/IP | OS: | Windows (XP version 2002 SP3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | autoincrement, temporary table |
[19 Nov 2009 11:59]
KREME LANDRY KOSSONOU
[19 Nov 2009 12:42]
Valeriy Kravchuk
Thank you for the problem report. Please, send the code of your procedure and SHOW CREATE TABLE results for the temporary table used.
[19 Nov 2009 13:10]
Valeriy Kravchuk
What is your default storage engine?
[19 Nov 2009 13:33]
KREME LANDRY KOSSONOU
My default storage engine is InnoDB
[19 Nov 2009 13:43]
Valeriy Kravchuk
So, temporary table is created as InnoDB one. Please, send the results of: show variables like 'innodb_autoinc%';
[19 Nov 2009 16:33]
Valeriy Kravchuk
So, you have: "innodb_autoinc_lock_mode","1" Please, check if setting it to 0 will help to get the results you expect. Read http://dev.mysql.com/doc/refman/5.1/en/innodb-auto-increment-handling.html and http://dev.mysql.com/doc/refman/5.1/en/innodb-parameters.html#sysvar_innodb_autoinc_lock_m... for the details.
[20 Nov 2009 12:28]
KREME LANDRY KOSSONOU
After configuration of the auto_inc_lock_mode option to zero (0) all the autoincrement work correctly (without gap) since there is no rollback. Thank you for the help.
[20 Nov 2009 12:31]
KREME LANDRY KOSSONOU
The configured option is innodb_autoinc_lock_mode = 0 Thank
[21 Nov 2009 15:45]
Valeriy Kravchuk
So, this was problem was not related to any bug, but was a result of a (documented) change in default behavior of auto_increment columns of InnoDB tables in 5.1.x.