| From: | "Stewart Ben (RBAU/EQS4) *" <Ben(dot)Stewart(at)au(dot)bosch(dot)com> |
|---|---|
| To: | <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Update timestamp on update |
| Date: | 2005-10-13 02:56:53 |
| Message-ID: | E253BDD7F008244585AEE87AF8F0224F116C7ACE@cl-mail01.au.bosch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> 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.
>
> 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(dot)stewart(at)au(dot)bosch(dot)com
http://www.bosch.com.au/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthony Molinaro | 2005-10-13 03:02:40 | Re: pg, mysql comparison with "group by" clause |
| Previous Message | Tom Lane | 2005-10-13 02:52:04 | Re: [SQL] Update timestamp on update |