|
Mike- If I understand your question you could use a 'row-trigger' http://download.oracle.com/docs/cd/B10501_01/server.920/a96524/c18trigs.htm#1907 specificy initial filtering thru 'Trigger Restriction' consequent specifics of which row to process can be handled in the 'Trigger Action' Anyone else? Martin ______________________________________________ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. > Date: Thu, 26 Jun 2008 10:29:30 -0500 > From: shulman@xxxxxxxxxxxx > To: dean_rasheed@xxxxxxxxxxx > Subject: Re: [GENERAL] what are rules for? > CC: pgsql-general@xxxxxxxxxxxxxx; tgl@xxxxxxxxxxxxx; kleptog@xxxxxxxxx; adam.r@xxxxxxxxxxxxx > > On Thu, Jun 26, 2008 at 5:08 AM, Dean Rasheed <dean_rasheed@xxxxxxxxxxx> wrote: > > The Oracle "instead of" trigger ducks this issue completely. The > > trigger is called once per row in the view that matches the top-level > > "where" clause, and it is entirely up to the author of the trigger > > function to work out what to update (if anything). > > That sounds like exactly the sort of thing I was envisioning. > Although from what Tom said, it sounds as though "instead of" triggers > in PostgreSQL would have to be implemented in a significantly > different way from other triggers. > > How does an Oracle "instead of" trigger decide how many rows to tell > the caller were updated? Can this "return value" be modified > programmatically by the trigger? > > Mike > > -- > Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general Need to know now? Get instant answers with Windows Live Messenger. IM on your terms. |
