Bug #5369 wrong initial value of auto increment in mysql cluster

• Submitted: 2 Sep 2004 15:48
• Modified: 10 Sep 2004 17:17
• Reporter: Tomas Ulin
• Status: Closed
• Category: MySQL Cluster: Cluster (NDB) storage engine
• Severity: S3 (Non-critical)
• Version: 4.13, 4.1.4
• OS: Any (any)
• Assigned to: Tomas Ulin
• CPU Architecture: Any

[2 Sep 2004 15:48] Tomas Ulin

Description:
An auto_increment column in a NDB table starts its generated values from 
zero instead of 1.

Test done using MySQL-max 4.1.3, binaries compiled by MySQL AB
(mysql-max-4.1.3-beta-pc-linux-i686.tar.gz)

Cheers

gmax

--------------------------------------------------------
How to reproduce the bug:

mysql> create table ndbtest (i int not null auto_increment primary key) 
engine=ndb;

mysql> create table myisamtest (i int not null auto_increment primary 
key) engine=myisam;

mysql> create table innodbtest (i int not null auto_increment primary 
key) engine=innodb;

mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| innodbtest     |
| myisamtest     |
| ndbtest        |
+----------------+

mysql> insert into innodbtest values (NULL);
mysql> insert into myisamtest values (NULL);
mysql> insert into ndbtest values (NULL);

mysql> select * from myisamtest;
+---+
| i |
+---+
| 1 |
+---+

mysql> select * from innodbtest;
+---+
| i |
+---+
| 1 |
+---+

mysql> select * from ndbtest;
+---+
| i |
+---+
| 0 |
+---+

How to repeat:
see above

[10 Sep 2004 17:17] Tomas Ulin

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html