Date: Thu, 13 Oct 2005 12:20:43 -0500
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Williams <jeffw@globaldial.com>, pgsql-sql@postgresql.org,
	pgsql-docs@postgresql.org
Subject: Re: [SQL] Update timestamp on update
Message-ID: <20051013172042.GZ23883@pervasive.com>
References: <434DB482.1000205@globaldial.com> <16305.1129167889@sss.pgh.pa.us>
	<434DC97E.7000603@globaldial.com> <16842.1129171924@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16842.1129171924@sss.pgh.pa.us>
User-Agent: Mutt/1.5.9i

On Wed, Oct 12, 2005 at 10:52:04PM -0400, Tom Lane wrote:
> Jeff Williams <jeffw@globaldial.com> writes:
> > Thanks. Triggers was my first thought, but chapter 35 on Triggers didn't
> > really indicate a way I could do this easily and scared me with a lot of
> > c code.
> 
> Yeah.  This is a documentation issue that's bothered me for awhile.
> 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.

Chapter 35 is plpgsql.. do you mean chapter 32.4?

> Anybody have a better idea?

What about a See Also section ala man pages that links to trigger info
for other languages?
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461