And now I just got yet another email for a different bug from 2008!! What's going on here?
BTW, this bug is super annoying! How sad that in FOUR YEARS AND FOURTEEN DAYS it is yet to be fixed. Seriously? This can't be that hard to fix, in fact, it seems that Innodb would have to go out of it's way to be different than the standard SQL logic. > -----Original Message----- > From: Daevid Vincent [mailto:dae...@daevid.com] > Sent: Monday, August 02, 2010 12:35 PM > To: 'MySQL List' > Subject: There is something wrong with bugs.mysql.com email > server I think. > > I don't know if anyone from mysql is monitoring this list, but I think > there is something goofy going on with your email servers. I > just now got > this email below. Uhm. I wrote that bug over a year and a > half ago, and the > reply by Susanne was the day after. WTF? > > ...better late than never I suppose, but maybe you should > look into your > mail server Q and see if there are more "stuck" emails?! -----Original Message----- From: Bug Database [mailto:do-not-re...@mysql.com] Sent: Sunday, August 01, 2010 4:04 AM To: dae...@daevid.com Subject: #21641 [Ver]: nonpreserving of InnoDB auto_increment values can lead to unintended inheritance Unsubscribe from updates to this bug at: http://bugs.mysql.com/21641 Updated by: Shane Bester Reported by: Stephen Dewey Category: Server: InnoDB Severity: S4 (Feature request) Status: Verified -Version: 4.1.20 +Version: 4.1, 5.1, 5.5 -OS: Linux +OS: Any -OS Details: Linux (Red Hat) +OS Details: Tags: auto_increment, innodb Defect Class: D5 (Feature request) [20 Oct 2008 23:40] Mattias Jonsson Closed bug#34077 as a duplicate of this. ------------------------------------------------------------------------ [13 Feb 2008 23:29] Dave Latham The current functionality is definitely not intuitive. A persistent auto-increment would be much appreciated! ------------------------------------------------------------------------ [19 Dec 2007 22:59] Mike Schumacher I agree that this is a critical problem that needs to be addressed. We are having all kinds of issues related to it. What is the status of this bug? ------------------------------------------------------------------------ [4 Jun 2007 22:06] Dimitriy Alekseyev What's the status of this feature request? ------------------------------------------------------------------------ [8 May 2007 3:20] Daevid Vincent This bug is critical and is causing us all kinds of grief with database integrity. Please escalate it. mysqladmin create INNODB_IS_BROKEN locutus ~ # mysql INNODB_IS_BROKEN mysql> CREATE TABLE `foo` ( -> `id` int(10) unsigned NOT NULL auto_increment, -> `name` varchar(20), -> PRIMARY KEY (`id`) -> ) ENGINE=INNODB; Query OK, 0 rows affected (0.01 sec) mysql> INSERT INTO foo values (null, 'a'); mysql> INSERT INTO foo values (null, 'b'); mysql> INSERT INTO foo values (null, 'c'); mysql> SELECT * FROM foo; +----+------+ | id | name | +----+------+ | 1 | a | | 2 | b | | 3 | c | +----+------+ 3 rows in set (0.00 sec) mysql> DELETE FROM foo; Query OK, 3 rows affected (0.00 sec) mysql> QUIT; locutus ~ # /etc/init.d/mysql restart * Stopping mysql ... * Starting mysql (/etc/mysql/my.cnf) locutus ~ # mysql INNODB_IS_BROKEN mysql> INSERT INTO foo values (null, 'd'); Query OK, 1 row affected (0.01 sec) mysql> SELECT * FROM foo; +----+------+ | id | name | +----+------+ | 1 | d | +----+------+ 1 row in set (0.00 sec) ------------------------------------------------------------------------ [28 Aug 2006 13:08] Valeriy Kravchuk Thank you for a reasonable feature request. ------------------------------------------------------------------------ Earlier comments can be viewed at http://bugs.mysql.com/21641 -- http://bugs.mysql.com/21641 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
