At 16:49 +0000 1/31/02, Jude Insley wrote:
>The SQL below illustrates what I believe is a bug in MySQL up to and
>including 3.23.47. Essentially I need a unique key where one or more of
>the component fields of the unique key can be NULL. What seems to happen
>is that you can add "duplicate" rows if the value is NULL.
This is how UNIQUE indexes work in MySQL. All values except NULL
must be unique. If you use a PRIMARY KEY instead, this won't happen.
Of course, the reason it won't happen is that PRIMARY KEY disallows
Why does UNIQUE behave that way? I suppose because NULL != NULL.
>Has anyone come across this before? Is this a bug?
>Wide Area Communications