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>, Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Return type of triger functions from OPAQUE to TRIGGER in 7.3
Date: Wed, 26 Feb 2003 09:08:14 -0800
User-Agent: KMail/1.4.3
Cc: pgsql-sql@postgresql.org
References: <20030225192043.GA30324@cc.usu.edu>
	<12893.1046207414@sss.pgh.pa.us> <20030226044826.GC8564@cc.usu.edu>
In-Reply-To: <20030226044826.GC8564@cc.usu.edu>
MIME-Version: 1.0
Message-Id: <200302260908.14180.josh@agliodbs.com>
Content-Transfer-Encoding: quoted-printable

Roberto,

> No, that was not what I was suggesting. I was suggesting (based on my
> assumption that 'create function ... returns opaque' would convert the
> return type to trigger), that its behaviour be made consistent with
> 'create or replace function' and throw an error if the type is opaque.

I can't see any way to do that without making it very difficult to upgrade =
to=20
7.3.

> For our next release, our plan was to have both 7.2 and 7.3
> compatibility. For the release after that, 7.2 compatibility would
> probably be dumped in favor of 7.3, where we could make use of 7.3-specif=
ic
> features. We wanted it to be a gradual path.

Where does OpenACS do its object creation?  Just at setup/install time, or=
=20
through the life of the program?   If the former, I'd suggest having two=20
seperate database install scripts ... one for 7.2.and one for 7.3.

--=20
Josh Berkus
Aglio Database Solutions
San Francisco