Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DAD12475C38 for ; Tue, 27 Aug 2002 18:38:15 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 35171475BD4 for ; Tue, 27 Aug 2002 18:38:15 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1626093; Tue, 27 Aug 2002 15:38:15 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Mathieu Arnold , pgsql-sql@postgresql.org Subject: Re: triggers and plpgsql question Date: Tue, 27 Aug 2002 15:38:45 -0700 X-Mailer: KMail [version 1.4] References: <374862253.1030472287@andromede.reaumur.absolight.net> In-Reply-To: <374862253.1030472287@andromede.reaumur.absolight.net> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200208271538.45877.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200208/369 X-Sequence-Number: 9215 Mathieu, > The thing I need, is to be able to know what does NEW contains, and I have > not found out any mean to do so. If it's not possible to do so, I'll write > a function per table, but for the beauty of all this, I would have liked = to > do it the way above. You can't do this in PL/pgSQL. See the online documentation on writing=20 triggers in C; that is the only way to get what you want. --=20 -Josh Berkus Aglio Database Solutions San Francisco