[MDEV-4531] TokuDB: Auto-increment on a secondary column is accepted, but causes gaps Created: 2013-05-14  Updated: 2013-05-20  Resolved: 2013-05-17

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.31
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: tokudb

Issue Links:
Relates
relates to MDEV-4507 Include TokuDB storage engine Closed

 Description   

CREATE TABLE t1 (a char(8), b int AUTO_INCREMENT, PRIMARY KEY (a,b)) ENGINE=TokuDB;
INSERT INTO t1 (a) VALUES ('a'),('b'),('c'),('d'),('e'),('f'),('g'),('h'),('i'),('j');
SELECT LAST_INSERT_ID();
LAST_INSERT_ID()
1
SELECT a,b FROM t1;
a	b
a	1
b	11
c	21
d	31
e	41
f	51
g	61
h	71
i	81
j	91

Test case:

install soname 'ha_tokudb.so';
 
CREATE TABLE t1 (a char(8), b int AUTO_INCREMENT, PRIMARY KEY (a,b)) ENGINE=TokuDB;
INSERT INTO t1 (a) VALUES ('a'),('b'),('c'),('d'),('e'),('f'),('g'),('h'),('i'),('j');
SELECT LAST_INSERT_ID();
SELECT a,b FROM t1;

bzr version-info
revision-id: holyfoot@askmonty.org-20130514121908-d6tp4zsdkim0q4dg
revno: 3768
branch-nick: 5.5-hf-tokudb



 Comments   
Comment by Elena Stepanova [ 2013-05-14 ]

Not reproducible on MariaDB-5.5.30-TokuDB-7.0.1

Generated at Thu Feb 08 06:57:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.