Triggers,throw errors?  I didn't know they could do that.  Other than via 
"raise notice", how is this done?  Could I capture such an error 
programatically (e.g. in perl/DBI)?



-----Original Message-----
From: Tom Lane [mailto:t...@sss.pgh.pa.us] 
Sent: Saturday, January 16, 2010 9:12 PM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Read only column ? 

"Gauthier, Dave" <dave.gauth...@intel.com> writes:
>> .. although, if you have triggers forcibly setting the columns, it
>> hardly matters what the users try to put into them, no?

> Ummmm..... Wellll....  I guess you have a point there :-)

> Still, it would be nicer for the DB to tell them "DON'T TOUCH THAT" as 
> opposed to a trigger silently overriding whatever they may have thought they 
> changed.

Well, you could have the triggers throw errors instead of being silent
about it.

                        regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to