Content-Type: text/plain;
  charset="iso-8859-1"
From: Josh Berkus <josh@agliodbs.com>
Organization: Aglio Database Solutions
To: Roberto Mello <rmello@cc.usu.edu>, pgsql-sql@postgresql.org
Subject: Re: Return type of triger functions from OPAQUE to TRIGGER in 7.3
Date: Tue, 25 Feb 2003 16:42:35 -0800
User-Agent: KMail/1.4.3
References: <20030225192043.GA30324@cc.usu.edu>
In-Reply-To: <20030225192043.GA30324@cc.usu.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200302251642.35425.josh@agliodbs.com>

Roberto,

> We found out a few days ago that in PG 7.3 the return type for trigger
> functions was redefined from OPAQUE to TRIGGER. What's the rationale
> behind this? Is this for standards compliance (forgive my ignorance about
> the standard's details)? Were there other gains to be obtained from this
> move?

Yes.  In < 7.3, OPAQUE actually referred to 3 different types of non-parsab=
le=20
return values.   Differntiating the different types should be an improvemen=
t=20
in both performance and error prevention.

> So right now we are stuck on either changing the return type of every
> trigger for TRIGGER (which means no 7.2 compatibility) or stay stuck in
> 7.2-land.

Seems to me that this could be done to the whole OpenACS package with a Per=
l=20
or Sed script.

--=20
Josh Berkus
josh@agliodbs.com
Aglio Database Solutions
San Francisco