Bug #71122 | auto_increment doesn't update after changing auto_increment_increment/offset | ||
---|---|---|---|
Submitted: | 10 Dec 2013 0:27 | Modified: | 19 Nov 2015 16:33 |
Reporter: | Nahuel Sotelo | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Information schema | Severity: | S4 (Feature request) |
Version: | 5.5.27 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | auto_increment, auto_increment_increment, auto_increment_offset |
[10 Dec 2013 0:27]
Nahuel Sotelo
[10 Dec 2013 19:19]
MySQL Verification Team
This two variables affect tables only at table creation. Later changes will only affect new tables that are yet to be created. If you find that this is not functional, please provide a test case.
[10 Dec 2013 19:29]
Nahuel Sotelo
I've already provided a test case! haha
[11 Dec 2013 19:14]
MySQL Verification Team
What I wrote that this would be a bug if you provided a test case where table would be created AFTER auto_increment_increment/_offset were changed.
[11 Dec 2013 19:16]
Nahuel Sotelo
So, this is not a bug? What is it then? A feature request? It would be desirable that the AUTO_INCREMENT would return automatically the right value... I don't say to be done automatically after the my.cnf is changed but maybe through performing a REPAIR TABLE or something like that. What do you say about that?
[16 Dec 2013 17:21]
Nahuel Sotelo
Hey guys, I have a database with relational ids and so, I cannot re-create the tables again. That would be a very risky job. It would be easier if the auto_increment option of the table would update automatically to the new increment/offser without having to re-create the tables...
[19 Nov 2015 16:33]
Georgi Kodinov
Thank you for the reasonable feature request to take into account these two variables when calculating the I_S values.