Hi, We have just started out using Innodb tables to get maximum performance when we have a large number of users fairly simultaneously accessing some of our large tables. Row-locking is a good thing for us. That's why we like Innodb. But... there's a problem. One of our tables contains a unique index, which we need. And when I try and alter that table to be an Innodb table, I get:
Error 1062: Duplicate value 'NULL' in key 3. I thought that perhaps databases shouldn't allow NULL values in a UNIQUE index - obviously, if there are several NULL values for a field, a unique index would seem to be no good. But it seems that generally accepted practice is to allow NULL in a UNIQUE index. In which case, how can I get my UNIQUE index with NULLs to work with Innodb? Or is this a B U G? John Kemp Director, Software Development Streetmail, Inc. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
