Re: bug or feature, || -operator and NULLs

On Wed, 2006-10-18 at 15:57 +0200, Martijn van Oosterhout wrote:
> On Wed, Oct 18, 2006 at 03:44:05PM +0200, Andreas Joseph Krogh wrote:
> > > When in doubt, consult the standard ... Oracle's treatment of NULL is
> > > known to violate the standard, IIRC. Your measure of correctness seems
> > > to be "appears to me more logical", but ours is "complies with the
> > > standard".
> >
> > I know PG violates the standard in other places and core's favourite argument
> > for doing so is "the standard is braindead here, so we do it our way".
>
> But they're few and far between and not on things people actually
> notice much.
>
> What's being suggested simply violates common sense. Basically:
>
> if (a = b) then (a||c = b||c)
>

If a is 'x' and b is 'x' and c is NULL, the above statement doesn't hold
in PostgreSQL.

I'm not disagreeing with your overall point, I'm just missing what you
meant by the above statement. What are a, b, and c supposed to be?

Regards,
Jeff Davis