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

Re: comparing rows

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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:40:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> 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.

Well, I'm not sure.  Magnus is saying that the newer MS servers default
to spec-compliant semantics --- ie, foo = NULL will yield NULL.  But
IIRC the original complaints were because MS tools like Access would
*generate* this expression and expect it to behave like foo IS NULL.

Can MS have fixed all their apps already?  Seems unlikely.  Maybe we
have to leave the kluge in there awhile longer.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2000-08-03 14:56:30
Subject: Re: [HACKERS] random() function produces wrong range
Previous:From: Don BaccusDate: 2000-08-03 14:37:17
Subject: Re: comparing rows

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