SQL Developer 1.5: Mysql unique index problem

Question

I experienced a problem with SQL Developer 1.5: uniqueness of multiple fields indexes seems to be lost. On single field indexes it works properly.
As you can see generated code lacks the "UNIQUE" keyword
MySQL DDL:
CREATE TABLE `my_table` (
`aaa` CHAR(20) COLLATE latin1_swedish_ci NOT NULL DEFAULT '%',
`bbb` CHAR(4) COLLATE latin1_swedish_ci NOT NULL DEFAULT '',
`ccc` CHAR(4) COLLATE latin1_swedish_ci NOT NULL DEFAULT '%',
`ddd` CHAR(4) COLLATE latin1_swedish_ci NOT NULL DEFAULT '%',
`eee` CHAR(4) COLLATE latin1_swedish_ci NOT NULL DEFAULT '%',
`fff` CHAR(30) COLLATE latin1_swedish_ci NOT NULL DEFAULT '',
`ggg` CHAR(30) COLLATE latin1_swedish_ci DEFAULT NULL,
UNIQUE KEY `All` (`aaa`, `bbb`, `ccc`, `ddd`, `eee`, `fff`, `ggg`),
KEY `key_bbb` (`bbb`),
KEY `key_ccc` (`ccc`)
)ENGINE=MyISAM
ROW_FORMAT=FIXED CHARACTER SET 'latin1' COLLATE 'latin1_swedish_ci';
Generated code:
CREATE TABLE my_table \[...\]
CREATE INDEX All_ ON my_table
aaa,
bbb,
ccc,
ddd,
eee,
fff,
ggg
\[...\]

Answer 1

That looks strange. I created the following three tables in mySQL:
CREATE TABLE `my_table_a` (
`aaa` CHAR(20) ,
`bbb` CHAR(4) ,
UNIQUE KEY `All` (`aaa`, `bbb`),
KEY `key_aaa` (`aaa`),
KEY `key_bbb` (`bbb`)
CREATE TABLE `my_table_b` (
`aaa` CHAR(20) ,
`bbb` CHAR(4) ,
UNIQUE KEY `All` (`aaa`, `bbb`),
UNIQUE KEY `key_aaa` (`aaa`),
KEY `key_bbb` (`bbb`)
CREATE TABLE `my_table_c` (
`aaa` CHAR(20) ,
`bbb` CHAR(4) ,
UNIQUE KEY `All` (`aaa`, `bbb`),
KEY `key_aaa` (`aaa`),
UNIQUE KEY `key_bbb` (`bbb`)
The wrong result can already be seen in the captured model.
Result for my_table_a:
All: NON_UNIQUE
key_aaa: NON_UNIQUE
key_bbb: NON_UNIQUE
Result for my_table_b:
All: UNIQUE
key_aaa: UNIQUE
key_bbb: NON_UNIQUE
Result for my_table_c:
All: NON_UNIQUE
key_aaa: NON_UNIQUE
key_bbb: UNIQUE
So there is at least one case where an index with two segments is remaining UNIQUE. But as soon as the index has three segments, the UNIQUE is lost.
I'll check whether this is a known bug, and if not, I'll create a new bug.
Regards,
Wolfgang