DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=XND07mua7q69J7AXswRJVuwCiGG0hCUwzTXA+nxl4w1x5b/otUEQhVolYWOrJmg26e
	vYUzf1vDkaSkV+vq6G5aCtOdY0uT4Vy5QI1XslVbY3danwQAq4LXVrCeyF3WhOoX/vQd
	kMHS1SEtUc3F1/OUgju5flrWTBEpPP+JrjNPo=
MIME-Version: 1.0
In-Reply-To: <1102.1304649395@sss.pgh.pa.us>
References: <BANLkTi=Neok1uboh4P4jxuGWBpbOFH2wdQ@mail.gmail.com>
	<BANLkTikzDpBjvUmkoYFWQVPDOdmYX=KFKw@mail.gmail.com>
	<1102.1304649395@sss.pgh.pa.us>
From: Josh Kupershmidt <schmiddy@gmail.com>
Date: Thu, 5 May 2011 22:58:24 -0400
Message-ID: <BANLkTin=Z+JZLwXKOnNmxcDKt2aXr8p4vg@mail.gmail.com>
Subject: Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's
	triggers
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Stehule <pavel.stehule@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, May 5, 2011 at 10:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> That is, in fact, exactly the behavior you get if you declare a RECORD
> variable and set it to NULL. =A0If these variables were indeed not
> declared, you'd get a complaint about "new" not being a known variable.

Hrm, guess I learned something. I tested with a trigger function which used=
:
...
     IF NEW IS NULL THEN
       RAISE NOTICE 'new is null.';
...

which was giving me 'ERROR:  record "new" is not assigned yet' when
used as an on-delete trigger. I am a little surprised that you can't
use IS NULL to test out a record-type variable which you've just
declared to be NULL, e.g. this function blows up:

CREATE OR REPLACE FUNCTION test_trg() RETURNS TRIGGER AS $$
  DECLARE SOMEVAR record;
  BEGIN
     SOMEVAR :=3D NULL;
     IF SOMEVAR IS NULL THEN
       RAISE NOTICE 'somevar is null.';
     END IF;
  RETURN NEW;
  END;
$$ LANGUAGE plpgsql;

with the same error message.

Josh