Re: Read only column ?

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:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Saturday, January 16, 2010 9:12 PM
To: Gauthier, Dave
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Read only column ?

"Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)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