pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Phillip Smith <phillip.smith@weatherbeeta.com.au>
To: pgsql-sql@postgresql.org
Subject: Re: Proposed archival read only trigger on rows - prevent history modification
Date: Fri, 22 Feb 2008 15:09:11 +1100
Message-ID: <014801c87508$ada837d0$9b0014ac@wbaus090> (raw)
In-Reply-To: <200802212231.58019.xzilla@users.sourceforge.net>

On Tuesday 12 February 2008 03:25, Bryce Nesbitt wrote:
> Yes, the view approach has some advantages.  But it still leaves the 
> underlying tables naked to modification. And since the most likely 
> error is... well... me (or another admin) at the SQL prompt, we want 
> underlying tables protected also.

Couldn't you make a row trigger BEFORE UPDATE?

CREATE OR REPLACE FUNCTION readonly_handler()
  RETURNS "trigger" AS
$BODY$
	BEGIN
		IF OLD.read_only = TRUE THEN
			RETURN OLD;
		ELSE
			RETURN NEW;
		END IF;
	END;
$BODY$
LANGUAGE 'plpgsql' VOLATILE;


THINK BEFORE YOU PRINT - Save paper if you don't really need to print this

*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.



view thread (7+ messages)

Message-ID: <014801c87508$ada837d0$9b0014ac@wbaus090>
Permalink:  ../014801c87508$ada837d0$9b0014ac@wbaus090/
Also on:    postgresql.org/message-id/014801c87508$ada837d0$9b0014ac@wbaus090

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: phillip.smith@weatherbeeta.com.au
  Subject: Re: Proposed archival read only trigger on rows - prevent history modification
  In-Reply-To: <014801c87508$ada837d0$9b0014ac@wbaus090>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox