Tom Lane wrote:
> "Marin Dimitrov" <marin(dot)dimitrov(at)sirma(dot)bg> writes:
>
>>don't use NULLs
>
>
> I agree with Marin. If you think you need x = NULL to act like x IS
> NULL, then you should rethink the way you are using NULL in your data
> design. You are really swimming against the tide of the way that SQL
> specifies NULL to work.
>
> regards, tom lane
Has this change affected the behavior of the isnull
operator/keyword/whatever it is...
select * from tablename where foo isnull;
I use that on occasion (in 7.1.2)...did this change in 7.2 also?
--Jeremy