Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP
	id EA2D0476360; Thu, 29 Aug 2002 11:21:03 -0400 (EDT)
Received: from news.hub.org (news.hub.org [64.49.215.80])
	by postgresql.org (Postfix) with ESMTP
	id 92DD04762FF; Thu, 29 Aug 2002 11:21:03 -0400 (EDT)
Received: by news.hub.org (Postfix, from userid 8)
	id 46FE438198B; Thu, 29 Aug 2002 11:21:00 -0400 (EDT)
From: "Greg Patnude" <GPatnude@adelphia.net>
X-Newsgroups: comp.databases.postgresql.general,
	comp.databases.postgresql.questions,
	comp.databases.postgresql.sql
Subject: Why must the function that a trigger calls return "opaque" ???
Date: Thu, 29 Aug 2002 08:35:42 -0700
Organization: Hub.Org Networking Services (http://www.hub.org)
Lines: 9
Message-ID: <akle4r$2nq5$1@news.hub.org>
X-Complaints-To: news@hub.org
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
To: pgsql-general@postgresql.org, pgsql-sql@postgresql.org
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200209/68
X-Sequence-Number: 29649

This seem rather limiting...  Suppose I want a trigger that after insert,
returns the currval(sequence) of the newly inserted row automatically
without having to run another query ???

GP