Re: comparing NEW and OLD (any good this way?)

On 2009-07-23, Sam Mason <sam@samason.me.uk> wrote:
> On Thu, Jul 23, 2009 at 01:45:36PM +0200, Pavel Stehule wrote:
>> http://www.postgres.cz/index.php/PostgreSQL_SQL_Tricks
>
> Just had a quick flick through your list and one of the early ones stuck
> out:
>
>
http://www.postgres.cz/index.php/PostgreSQL_SQL_Tricks#Attention_on_IS_NULL_and_IS_NOT_NULL_operators_for_composite_types
>
> is scary; even worse is that it was changed to be like this in 8.2
> because the standard says it should behave this way.  What on earth were
> they thinking when they defined the standard this way?

since any comparson involving those tuples will return NULL true is the
correct value for IS NULL

if you are bothered by this behavior you are misusing NULL.