Bug #27120 | MySQL Table Editor accepts questionable value for 'Auto Increment' field | ||
---|---|---|---|
Submitted: | 14 Mar 2007 8:42 | Modified: | 26 May 2009 13:03 |
Reporter: | Heinz Schweitzer (Gold Quality Contributor) | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Administrator | Severity: | S3 (Non-critical) |
Version: | 1.2.10 | OS: | Windows (XP, Mac OS X) |
Assigned to: | CPU Architecture: | Any |
[14 Mar 2007 8:42]
Heinz Schweitzer
[14 Mar 2007 9:25]
Sveta Smirnova
Thank you for the report. But according to http://dev.mysql.com/doc/refman/5.0/en/create-table.html it is expected behavior: For engines that support the AUTO_INCREMENT table option in CREATE TABLE statements, you can also use ALTER TABLE tbl_name AUTO_INCREMENT = N to reset the AUTO_INCREMENT value. The value cannot be set lower than the maximum value currently in the column. There is nothing about high value. You can insert value into auto_increment field manually.
[14 Mar 2007 9:42]
Heinz Schweitzer
I know that I can set the auto increment value manualy, however it is strange that my value '123456789012345678901234567890' is mapped to '9223372036854775807' and finally ends up as '1' in the data base, and in between I am not able to insert records into this table. Some sort of notification in case of mapping values would be nice.
[14 Mar 2007 10:38]
Sveta Smirnova
Thank you for the additional comment. You are right although SHOW CREATE TABLE ouputs AUTO_INCREMENT=18446744073709551615 MySQL GUI Tools show other auto_increment value for same table.
[26 May 2009 13:03]
Susanne Ebrecht
Many thanks for writing a bug report. We are on the way to implement full functionality of MySQL Administrator into MySQL Workbench. We won't add this feature request anymore. More informations about MySQL Workbench you will find here: http://dev.mysql.com/workbench/