PS. Again, what do I know? Rumor has it my older
siblings dropped me on my
head when I was an infant. ;-)
Hi Dan,
I believe that the Sybase behavior is correct. I
have logged bug 653 to
track this issue.
Regards,
-Rick
Dan Meany wrote:
I noticed that in Derby a unique
behave differently.
Dan
--- Michael J. Segel [EMAIL PROTECTED] wrote:
On Thursday 27 October 2005 07:40, Dan Meany wrote:
The posted code does not provide a workaround as
it
does not allow duplicate rows with nulls:
INSERT INTO foo VALUES (6, NULL);
INSERT INTO foo VALUES (6, NULL
DB2, at least with the version/settings we have, seems
to be able to do a CREATE UNIQUE INDEX WHERE NOT NULL,
but not MS SQL Server.
Here's a further discussion of this topic...
http://weblogs.sqlteam.com/davidm/archive/2004/05/21/1364.aspx
I noticed that in Derby a unique constraint on two
columns A and B, with B nullable, will prevent
inserting two identical records that contain NULL in
B.
This is different from some other databases such as
Sybase that do allow it (I assume where the null
records are not in stored as part of the
