uBois
Asunto: Re: Bug in UNIQUE?
In the last episode (Feb 01), Carsten Gehling said:
> > >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
In the last episode (Feb 01), Carsten Gehling said:
> > >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
From: "Paul DuBois" <[EMAIL PROTECTED]>
To: "Jude Insley" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Subject: Re: Bug in UNIQUE?
> >The SQL below illustrates what I believe is a bug in MySQL up to and
> >including 3.23.47. Essentially I need
At 16:49 + 1/31/02, Jude Insley wrote:
>Hi,
>
>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
Hi,
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.
Has anyone come
