Your message dated Wed, 08 Sep 2010 13:16:07 +0300
with message-id <[email protected]>
and subject line Closing very old Mysqld bugs (fixed during the etch cycle)
has caused the Debian Bug report #372813,
regarding mysql-server-4.1: No AUTO_INCREMENT=n with InnoBD
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
372813: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372813
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server
Severity: important
Cannot set the next auto_increment value in CREATE TABLE and
ALTER TABLE statements. No error message is returned, mysql
server just silently skip the command. For example:
CREATE TABLE `test` (
`id` int(11) NOT NULL auto_increment,
`txt` varchar(100) NOT NULL default '',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=11;
INSERT INTO `test` (`txt`) VALUES ('should be 11');
INSERT INTO `test` (`txt`) VALUES ('should be 12');
SELECT * FROM `test`;
+----+--------------+
| id | txt |
+----+--------------+
| 1 | should be 11 |
| 2 | should be 12 |
+----+--------------+
This prevents loading SQL dumps with saved auto increment
values and creating databases with non 1-based auto increment
primary keys, such as a user database starting with uid=10001.
The same issue reproduced using the ALTER TABLE command.
The bug can be reproduced using the mysql command line client,
PHPMyAdmin or anything else that can run SQL commands.
This feature should work starting with mysql-server 4.1.2.
SQL dumps with stored auto_increment values cannot be restored
correctly, that prevents correct backup of databases sensitive
for this kind of bug.
mysql-server version 4.1.11 from Debian stable does not work
correctly. mysql-server version 4.1.15 from Debian unstable
handles the above command correctly and sets the
auto increment value as requested. ALTER TABLE also works
for 4.1.15.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.15-1-686-smp
Locale: LANG=hu_HU, LC_CTYPE=hu_HU (charmap=ISO-8859-2)
--- End Message ---
--- Begin Message ---
Version: 4.1.7-1
This bug was reported back when the bts didn't have version tracking, and the
maintainer apparently forgot to close this bug when etch was released.
The maintainer claims in the bug report log that the reported problem was
fixed in upstream Mysql version 4.1.2, and according to the changelog the
first fixed version uploaded to Debian unstable was 4.1.7-1.
--
Arto Jantunen
--- End Message ---
