Hi Heikki,
I have proven this in MySQL 3.23.47 and I have found a problem with
CHECK TABLE, that reports error - corrupted table if there are
several NULL's in a UNIQUE index.
Happy end of year to all!,
José Ceferino Ortega
-Mensaje original-
Hi!
I will change InnoDB so that it allows
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
Hi!
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 values, because in
SQL NULL really means 'an unknown value'.
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 values,
