Message-ID: <3EA974B7.4090309@cvc.net>
Date: Fri, 25 Apr 2003 10:47:35 -0700
From: Dennis Gearon <gearond@cvc.net>
Reply-To: gearond@cvc.net
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.3b) Gecko/20030210
MIME-Version: 1.0
To: josh@agliodbs.com
Cc: Robert Treat <xzilla@users.sourceforge.net>, elein@varlena.com,
	elein <elein@sbcglobal.net>,
	"pgsql-general@postgresql.org" <pgsql-general@postgresql.org>,
	pgsql-sql@postgresql.org
Subject: Re: [SQL] rewriting values with before trigger
References: <1051201544.4753.522.camel@camel>
	<200304250033.h3P0XuDl088102@pimout1-ext.prodigy.net>
	<200304250003.24506.xzilla@users.sourceforge.net>
	<200304251020.48678.josh@agliodbs.com>
In-Reply-To: <200304251020.48678.josh@agliodbs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

It's a lot of work to write the functions, but it is the best way to keep the db intact.

Josh Berkus wrote:
> Robert,
> 
> 
>>You misunderstood. I don't think it's a bug in postgresql,  it's a bug in 
> 
> the 
> 
>>application that is hitting against my database. When it doesn't have a 
> 
> value 
> 
>>for the timestamp field, it either needs to drop it from the insert statment 
>>or convert it to null; not send a ''
> 
> 
> Incidentally, this sort of problem is why most of my apps are based on "push" 
> data functions.    i.e., instead of the client calling:
> INSERT INTO foo VALUES ( id, bar1, bar2, bar3 );
> it calls
> SELECT df_modify_foo ( id, bar1, bar2, bar3 );
> 
> Data-push functions allow me to do a whole array of validation and custom 
> error message return that would be impractical with triggers.   It also 
> allows me to build security checks in to the back-end, via:
> 
> SELECT df_modify_foo ( user_id, session_key, id, bar1, bar2, bar3 )
> 
> ... allowing me to check all of the following things:
> Does the user have a valid session?
> Does the user have rights to foo?
> Does the user have a lock on foo?
> Is this a new foo record, or a modified one?
> etc.
>