On Mon, 11 Mar 2002, Bhuvan A wrote:
> > If you compare a NULL with anything you don't get a true value whether
> > you're comparing with =, !=, <, >, etc... That's how it's defined to
> > behave.
> where did you get this definition of behaviour!? is it applicable only to
> postgres or ..? its quite strange yaar!
It makes sense if you think of NULL as an unknown value. You don't know
if this unknown value is different from any particular value (even another
NULL). NULLs are one of the ugliest parts of SQL.
In case you're wondering for SQL92 (at least the draft I have), the
section is 8.2 <comparison predicate>, General Rules 1.
1) Let X and Y be any two corresponding <row value constructor
element>s. Let XV and YV be the values represented by X and Y,
a) If XV or YV is the null value, then "X <comp op> Y" is un-
In response to
- at 2002-03-11 10:26:50 from Bhuvan A
- Re: at 2002-03-11 20:12:07 from Juliano Ignacio
pgsql-bugs by date
|Next:||From: Mozilla at Marela||Date: 2002-03-11 17:59:31|
|Subject: Critical: Pgsql inserts bad timestamp (seconds 60.00) - causes failing of backup-restore|
|Previous:||From: Peter Eisentraut||Date: 2002-03-11 16:46:31|
|Subject: Re: |