X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 48A10D832D for ; Wed, 12 Oct 2005 23:56:55 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84231-06 for ; Thu, 13 Oct 2005 02:56:49 +0000 (GMT) Received: from smtp-v.fe.bosch.de (smtp-v.fe.bosch.de [139.15.237.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9F33CD8320 for ; Wed, 12 Oct 2005 23:56:51 -0300 (ADT) Received: from mta2.fe.internet.bosch.com (unknown [10.4.98.30]) by imta6.fe.bosch.de (Postfix) with ESMTP id C35883804C for ; Thu, 13 Oct 2005 04:56:56 +0200 (CEST) Received: from mailgate.cl.internet.bosch.com (virusscan6.fe.internet.bosch.com [10.4.98.11]) by mta2.fe.internet.bosch.com (Postfix) with ESMTP id E41388C03C for ; Thu, 13 Oct 2005 04:56:55 +0200 (CEST) Received: from cl-mail01.au.bosch.com (unknown [10.23.5.53]) by mailgate.cl.internet.bosch.com (Postfix) with ESMTP id B61FF52829 for ; Thu, 13 Oct 2005 12:56:53 +1000 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Update timestamp on update Date: Thu, 13 Oct 2005 12:56:53 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [SQL] Update timestamp on update Thread-Index: AcXPoWyryx08Sk1GQguyRJjdA98bYQAABBTQ From: "Stewart Ben (RBAU/EQS4) *" To: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.488 required=5 tests=[AWL=0.114, DNS_FROM_RFC_ABUSE=0.374] X-Spam-Level: X-Archive-Number: 200510/123 X-Sequence-Number: 22976 > The problem is that we treat the PL languages as add-ons and therefore > the documentation of the "core" system shouldn't rely on them ... but > that leaves us presenting C-code triggers as the only examples in > chapter 35. There is a paragraph in there suggesting you go look at > the PL languages first, but obviously it's not getting the job done. >=20 > Anybody have a better idea? Include a sample trigger for each PL that is shipped with the standard distribution, along with comments to the effect that "it is suggested that the documentation for $PL is read before creating triggers"? It may also be worth including a comment that explicitly states that all(?) PLs are supported in triggers. Best regards, Ben Stewart -- Robert Bosch (Australia) Pty. Ltd. Engineering Quality Services, Student Software Engineer (RBAU/EQS4) Locked Bag 66 - Clayton South, VIC 3169 - AUSTRALIA mailto:ben.stewart@au.bosch.com http://www.bosch.com.au/=20