Re: Detecting changes to certain fields in 'before update' trigger functions - Mailing list pgsql-general

From Sebastian Tennant
Subject Re: Detecting changes to certain fields in 'before update' trigger functions
Date
Msg-id skp7iwrx.fsf@vps203.linuxvps.org
Whole thread Raw
In response to Detecting changes to certain fields in 'before update' trigger functions  (Sebastian Tennant <sebyte@smolny.plus.com>)
Responses Re: Detecting changes to certain fields in 'before update' trigger functions
List pgsql-general
Quoth Tom Lane <tgl@sss.pgh.pa.us>:
> Sebastian Tennant <sebyte@smolny.plus.com> writes:
>> I sometimes think this kind of gotcha is purposely buried, or not
>> addressed at all, in order to force users to read the manual.
>
> Where exactly do you think we should document it, if not in the
> manual?

I clearly didn't express myself very well.  Let me set the record
straight by saying that my experience with PostgreSQL over the past
three months or so has been fantastic, thanks in no small part to the
clear and comprehensive accompanying manual.

All I meant was that it sometimes _feels_ as if a vital piece of
information has been buried in the manual in order to make you read it.

(I wasn't making a serious point and I didn't expect it to be taken
literally).

Sebastian

P.S.  Emacs users of PostgreSQL might like to know that there's a
      texinfo version of the manual (version 8.3.3) available for
      download from here:

        http://www.emacswiki.org/PostGreSQL


pgsql-general by date:

Previous
From: "Andrus"
Date:
Subject: Re: db backup script in gentoo
Next
From: "Malinka Rellikwodahs"
Date:
Subject: Re: db backup script in gentoo