Re: Obtaining Firing Statement clause in (pl/perlu) Trigger Function

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Stef <stef(at)ummon(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Obtaining Firing Statement clause in (pl/perlu) Trigger Function
Date: 2005-05-23 17:26:27
Message-ID: 200505231026.27689.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stef,

> I am trying to write a function/Trigger in pl/perl (although any
> other language which allows this is perfectly fine with me :) and I need to
> find the firing statement. I understand that if the trigger was fired in
> a long sequence, then of course, the calling statement will be the
> previous trigger.

Talk to David Fetter (author of DBI-Link) about this. You're also probably
unnecessarily replicating his work.

It's not currently possible, unfortunately. Tge real way to do this would be
through RULES. However, RULEs currently don't give you a handle on query
substructures like where clauses (let alone join clauses). DF and I have
talked about it, but it would take some major back-end hacking to enable
it. :-(

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Bertheau 2005-05-23 18:33:39 ARRAY() returning NULL instead of ARRAY[] resp. {}
Previous Message Bruce Momjian 2005-05-23 16:42:10 Re: Speeding up the Postgres lexer