When doing a simple compare between 2 columns, UDB seems to be behaving
differently if there is a NULL value (probably following the ANSI standard
for treating NULL values).
If tablex has the folowing 2 columns
The following query :
If a != b
/* Do something */
in Sybase, would return the 2nd and 3rd rows, but in UDB, it would only
return the 2nd row. So is there a way in UDB to get the 2nd and 3rd row
(i.e: NULL should not be equal to 3).
I do know we can do a substitute value for NULL using COALASCE, but looking
for some config settings which can change this default NULL behavior.
thanks in advance.