Re: INSTEAD OF trigger on VIEWs

From: --= Tono =-- <tonodarmodjo(at)yahoo(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: INSTEAD OF trigger on VIEWs
Date: 2005-05-23 15:26:38
Message-ID: 20050523152638.27735.qmail@web53502.mail.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I have tried using INSTEAD rules but there are some
conditional logic that needs to happen inside the rule
(performing counts, getting and storing the primary
key of the master record etc.). AFAIK, rules only
allows conditional logic to be check prior to
execution of the rule and not inside the rule itself.
One way to get around this is to allow calling a
stored procedure inside the rule. This stored
procedure should have full access of NEW.* (and OLD.*
in the case of UPDATE and DELETE). This way the
manual INSERT, UPDATE or DELETE on the actual tables
can be performed from inside the stored procedure.

--- Christopher Kings-Lynne
<chriskl(at)familyhealth(dot)com(dot)au> wrote:
> You can probably just create an INSTEAD rule on the
> view...
>
> Chris
>
> --= Tono =-- wrote:
> > Is there any plans to create an INSTEAD OF trigger
> on
> > VIEWS? I have view which consists of a master
> and
> > detail table. When a row is inserted into the
> view,
> > the view needs to figure out if the master record
> > already exsists. If the record does not exists in
> the
> > master table, then insert into the master and the
> > detail table. If the record already exists in the
> > master, just insert into detail table.
> Conversely, if
> > a delete record is performed on the view, the view
> > needs to figure out if it only needs to delete
> from
> > the detail table, or should it also delete from
> the
> > master table when all the detail records are
> already
> > deleted. In Oracle this is easily done using
> INSTEAD
> > OF triggers. INSTEAD OF triggers can only be
> created
> > for VIEWs. The purpose of it is to "short-circuit"
> the
> > event (INSERT, UPDATE or DELETE) and perform
> whatever
> > is specified in the trigger.
> >
> > CREATE OR REPLACE TRIGGER schema.trigger_name
> INSTEAD
> > OF INSERT ON object_name
> > BEGIN
> > -- Perform the following instead --
> > END;
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam
> protection around
> > http://mail.yahoo.com
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the
> unregister command
> > (send "unregister YourEmailAddressHere" to
> majordomo(at)postgresql(dot)org)
>

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-05-23 15:42:31 Re: PATCH to allow concurrent VACUUMs to not lock each
Previous Message Douglas McNaught 2005-05-23 15:19:22 Re: inet increment w/ int8