From: | Mike Diehl <jdiehl(at)sandia(dot)gov> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: [DOCS] Update timestamp on update |
Date: | 2005-10-13 17:45:16 |
Message-ID: | 200510131145.16911.jdiehl@sandia.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-sql |
Is a working example something that people would like to see? Or is this
considered a good use of research time?
On Thursday 13 October 2005 11:20 am, Jim C. Nasby wrote:
> On Wed, Oct 12, 2005 at 10:52:04PM -0400, Tom Lane wrote:
> > Jeff Williams <jeffw(at)globaldial(dot)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?
--
Mike Diehl,
Network Monitoring Tool Devl.
SAIC at Sandia National Laboratories.
(505) 284-3137
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-10-13 18:02:14 | List of tables, figures and examples |
Previous Message | Bruce Momjian | 2005-10-13 17:33:16 | Re: [HACKERS] Added documentation about caching, reliability |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2005-10-13 18:26:58 | Re: pg, mysql comparison with "group by" clause |
Previous Message | Jim C. Nasby | 2005-10-13 17:20:43 | Re: [SQL] Update timestamp on update |