Jose,
thank you for the bug report. You are right: if there are several NULLs in a
unique secondary index, CHECK TABLE will report table corruption because of
a duplicate key in the index. I forgot to ease the check in CHECK TABLE.
I have now fixed this for 3.23.48.
Regards,
Heikki
Innobase O
SQL/InnoDB support at https://order.mysql.com/
>I have found a "problem" with UNIQUE in InnoDB.
>
>Example:
>
>mysql> CREATE TABLE b (
>-> idB int(11) NOT NULL auto increment,
>-> valor int(11) default NULL,
>-> PRIMARY KEY (idB),
>
On Sun, Dec 16, 2001 at 09:33:06PM +0200, Heikki Tuuri wrote:
> I will change InnoDB so that it allows several NULL values in secondary
> indexes even if that index would have been declared UNIQUE. Oracle has a
> similar convention.
>
> In the case of foreign keys, I advise against using NULL val
der commercial MySQL/InnoDB support at https://order.mysql.com/
>I have found a "problem" with UNIQUE in InnoDB.
>
>Example:
>
>mysql> CREATE TABLE b (
>-> idB int(11) NOT NULL auto increment,
>-> valor int(11) default NULL,
>-> PRIMARY KE
I have found a "problem" with UNIQUE in InnoDB.
Example:
mysql> CREATE TABLE b (
-> idB int(11) NOT NULL auto_increment,
-> valor int(11) default NULL,
-> PRIMARY KEY (idB),
-> UNIQUE KEY valor (valor)
-> ) TYPE=MyISAM;
Query OK, 0 row
