>> Another amusing example is how MSSQL handles UNIQUE consraints with
>> NULLable fields compared to all others. ;-))
>
> Yep. [1] But it's already in MS's tracker (link in post), hope they fix
> it.
>
> [1] http://blog.cincura.net/230837-unique-constraint-on-ms-sql/

For the record, if you want a CONSTRAINT, then create a CONSTRAINT,
not an INDEX.


Oh, and accepting one NULL is per SQL standard, a higher standard support
level requires accepting multiple NULLs. It's not as strange as you think, I
believe Firebird only recently changed this.

With regards,

Martijn Tonies
Upscene Productions
http://www.upscene.com

Download Database Workbench for Oracle, MS SQL Server, Sybase SQL
Anywhere, MySQL, InterBase, NexusDB and Firebird!

Database questions? Check the forum:
http://www.databasedevelopmentforum.com