Re: WHERE <timestamp-val>=NULL malfunction in release 7.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ingo Ciechowski <ciechowski(at)cis-computer(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: WHERE <timestamp-val>=NULL malfunction in release 7.2
Date: 2002-06-21 17:15:56
Message-ID: 20838.1024679756@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ingo Ciechowski <ciechowski(at)cis-computer(dot)com> writes:
> i++=# select * from uri where freigegeben=NULL;

This is not a bug; the 7.1.* behavior is the bug.

But see transform_null_equals if your application logic depends on
the old non-spec-compliant behavior.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2002-06-21 18:58:04 Re: regex (not) matching null string
Previous Message Bruno Wolff III 2002-06-21 17:13:42 Re: WHERE <timestamp-val>=NULL malfunction in release 7.2