Message-ID: <3A8AC8BD.EDCBC71A@agliodbs.com>
Date: Wed, 14 Feb 2001 10:04:45 -0800
From: Josh Berkus <josh@agliodbs.com>
Reply-To: josh@agliodbs.com
Organization: Aglio Database Solutions
MIME-Version: 1.0
To: sqllist <pgsql-sql@postgresql.org>
Subject: Re: Re: Trigger question
References: <3A8754BB.382CBDBE@wedwick.com> <3A8A9EF5.8C8929C@wedwick.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dave,

Please look at the docs for creating triggers.
(http:/www.postgresql.org/docs/).
Hopefully, someone on this list with more experience with Update and
Insert triggers can give you some help in avoiding the classic problems,
such as infinite loops.

Let me ask the obvious question:
If the InsertTime field is not open to user input, why are you providing
users with a data-entry interface for this field at all?  Why not hide
it, or display it read-only?

					-Josh Berkus
-- 
______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
   Complete information technology      josh@agliodbs.com
    and data management solutions       (415) 565-7293
   for law firms, small businesses       fax  621-2533
    and non-profit organizations.       San Francisco