Skip site navigation (1) Skip section navigation (2)

Re: comparing rows

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: comparing rows
Date: 2000-08-03 14:24:28
Message-ID: 200008031424.KAA20037@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> Magnus Hagander <mha(at)sollentuna(dot)net> writes:
> > Summary of MS:
> > When it runs in ANSI mode, null != null.
> > When it runs in backwards compatible mode , null=null.
> 
> Oh, that's interesting, they fixed their bug.
> 
> foo = NULL should produce NULL (*not* true, and *not* false either,
> though it'd act like false in a CASE test).
> 
> Here is one vote for ripping out our parser kluge and making null act
> like it should according to the spec.  Comments?

I thought our only kludge was allowing = NULL because we got tons of MS
folks complaining in the past before we did this.  Are you thinking that
the newer MS versions will not give us a problem.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-hackers by date

Next:From: Don BaccusDate: 2000-08-03 14:32:36
Subject: Re: comparing rows
Previous:From: Tom LaneDate: 2000-08-03 14:23:15
Subject: Re: comparing rows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group