/ All posts
- SQL9 NVARCHAR NULLs and the <> Operand
In Release 8 a query
SELECT * FROM [t] WHERE [c] <> "this value"
returns all rows where the value in [c] is 'not equal to' "this value" and also those rows where there is no value stored in [c].
In Release 9, when running that same query, those rows where 'there is no value stored in [c]' are not returned.
Is this change meant to bring SQL9 into compliance with a broader standard or norm? It results in having to rewrite query syntax to handle NULLs in nvarchar fields in 9, adding an "OR [c] IS NULL" to every statement; not the end of the world, but also an unwelcome discovery.
Thank you tjhb. This change seems to bring 9 into line with the RDBMS I use (PostgreSQL) as well, so this is likely for the best.