> From: "Dennis Fogg"
> > I'm getting lots of duplicate rows even though I have a
> > unique index defined over multiple columns.
> > The issue is that multiple NULL values are allowed,
> > even when some values are not null.
> > This could be as specified by the SQL standard,
> > but it's certai
From: "Dennis Fogg"
> I'm getting lots of duplicate rows even though I have a
> unique index defined over multiple columns.
> The issue is that multiple NULL values are allowed,
> even when some values are not null.
> This could be as specified by the SQL standard,
> but it's certainly confusing fo
I think you should review the very recent thread "why NOT NULL in
PRIMARY key??" which might shed some light on your particular issue.
In a nutshell, NULL!=NULL, so the database engine can not detect the
duplicate rows, as is expected.
-Hank
On 5/4/05, Dennis Fogg <[EMAIL PROTECTED]> wrote:
> I'
I'm getting lots of duplicate rows even though I have a
unique index defined over multiple columns.
The issue is that multiple NULL values are allowed,
even when some values are not null.
This could be as specified by the SQL standard,
but it's certainly confusing for the developer.
(By the way, on
