Bug 160569

Summary:

Using enums in multiple column primary keys is handled wrong in InnoDB storage engine

Product:

[Fedora] Fedora

Reporter:

Michal Piotrowski <bastian_knight>

Component:

mysql

Assignee:

Tom Lane <tgl>

Status:

CLOSED UPSTREAM

QA Contact:

David Lawrence <dkl>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

CC:

hhorak

Target Milestone:

---

Target Release:

---

Hardware:

i386

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2005-06-16 04:33:01 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Test case	none

Description Michal Piotrowski 2005-06-15 20:28:33 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
If you use InnoDB engine and create table with multiple column primary key where one of the columns is of enum type then it is handled wrong. MySQL reports duplicate keys where there aren't any.

Version-Release number of selected component (if applicable):
4.1.11-2

How reproducible:
Always

Steps to Reproduce:
1. Create table with multiple column primary key where one of the coulumns would be enum (for example int and enum).
2. Try to insert 2 rows, where there be changing only enum column.

  

Actual Results:  MySQL returns message like this:
ERROR 1062 (23000): Duplicate entry '1-b' for key 1

Expected Results:  Possible to add keys which are different only on the enum column.

Additional info:

This bug is registered in MySQL bug tracking system as bugs #9380 and and #9526 (http://bugs.mysql.com). There is a fix submitted.

Comment 1 Michal Piotrowski 2005-06-15 20:30:40 UTC

Created attachment 115506 [details]
Test case

To simplify testing I'm attaching this short SQL script.

Comment 2 Tom Lane 2005-06-16 04:33:01 UTC

We generally do not try to fix noncritical issues in advance of the upstream developers; for one reason, in 
this particular package we do not have the expertise to determine if a proposed fix is any good.  So my 
plan is to wait for a MySQL release in which this is fixed ...

Comment 3 Michal Piotrowski 2005-06-16 10:51:32 UTC

It would be great if there would be an update (a fix is done in MySQL version
4.1.12).