X-Original-To: pgsql-sql@postgresql.org
Received: from spampd.localdomain (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id CE790475E9D
	for <pgsql-sql@postgresql.org>; Thu, 24 Apr 2003 07:41:20 -0400 (EDT)
Received: from smtp.web.de (smtp03.web.de [217.72.192.158])
	by postgresql.org (Postfix) with ESMTP id E84AB474E42
	for <pgsql-sql@postgresql.org>; Thu, 24 Apr 2003 07:41:19 -0400 (EDT)
Received: from p508185db.dip0.t-ipconnect.de ([80.129.133.219] helo=web.de)
	by smtp.web.de with asmtp (TLSv1:RC4-MD5:128) (WEB.DE(Exim) 4.97 #53)
	id 198f6Q-0003e3-00
	for pgsql-sql@postgresql.org; Thu, 24 Apr 2003 13:41:22 +0200
Message-ID: <3EA7CD6A.9080404@web.de>
Date: Thu, 24 Apr 2003 13:41:30 +0200
From: Andreas Pflug <Andreas.Pflug@web.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Statement triggers 7.4 NEW/OLD
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=-10.9 required=5.0
	tests=BAYES_10,RCVD_IN_NJABL,USER_AGENT_MOZILLA_UA
	autolearn=ham	version=2.50
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
X-Archive-Number: 200304/358
X-Sequence-Number: 13059

How can I address the rows affected by an insert/update/delete statement 
in pl/pgsql?
The doc says that NEW and OLD will be NULL for statement triggers, which 
makes sense because NEW and OLD are of type RECORD, capable of holding 
only a single row.
So where's the beef?


Regards,
Andreas