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

Re: inconsistent composite type null handling in plpgsql out variable

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: inconsistent composite type null handling in plpgsql out variable
Date: 2009-08-31 17:21:41
Message-ID: 20090831172141.GG5407@samason.me.uk (view raw or flat)
Thread:
Lists: pgsql-bugs
On Fri, Aug 28, 2009 at 02:06:02PM -0400, Merlin Moncure wrote:
> 3) If we decide the sql standard is correct, so that (null, null) is
> null == true, then we should observe rule 1 and make things work in
> consistent way.  This means, for example, that null::foo and (null,
> null)::foo should not be distinct.

The more awkward case (to me anyway) is that the standard says (1,NULL)
IS NULL should evaluate to TRUE.

I'd never noticed the ROW / RECORD dichotomy before; could one of these
be made SQL compatible and the other use more sane semantics?

-- 
  Sam  http://samason.me.uk/

In response to

Responses

pgsql-bugs by date

Next:From: Pavel StehuleDate: 2009-08-31 17:26:59
Subject: Re: inconsistent composite type null handling in plpgsql out variable
Previous:From: Heikki LinnakangasDate: 2009-08-31 14:44:40
Subject: Re: psql: FATAL: the database system is in recovery mode

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