RE: UNIQUE in InnoDB

2001-12-31 Thread Heikki Tuuri
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

RE: UNIQUE in InnoDB

2001-12-31 Thread J. Ceferino Ortega
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 all

Re: UNIQUE in InnoDB

2001-12-16 Thread Michael T. Babcock
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

Re: UNIQUE in InnoDB

2001-12-16 Thread Heikki Tuuri
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'. Actually