From: | "Joe Conway" <jconway2(at)home(dot)com> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Fw: C function for use from PLpgSQL trigger |
Date: | 2001-02-04 08:04:00 |
Message-ID: | 022101c08e81$088d0980$0705a8c0@jecw2k1 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hello all,
I posted this (see below) Friday to the interfaces list with no response.
Does anyone know if what I'm trying to do is possible, or should I just
write the entire thing in a C function trigger? The latter would be
unfortunate because I think it would be nice to be able to extend PLpgSQL
using C functions like this.
Anyway, any help or advice will be much appreciated!
Thanks,
Joe
> Hi,
>
> I'm trying to create a C function that I can call from within a PLpgSQL
> trigger function which will return a list of all the values in the NEW
> record formatted suitably for an insert statement. I can't come up with a
> way to do this directly from within PLpgSQL (i.e. iterate through an
> arbitrary number of NEW.attribute).
>
> Can anyone tell me how I can either pass the NEW record to the C function
> (this produces an error message 'NEW used in a non-rule query') or gain
> access to the trigger tuple from within my C function? It seems that
> although PLpgSQL is called as a trigger, the C function is called as a
> regular function (makes sense) and thus has no access to the trigger tuple
> (my problem).
>
> Any help or guidance is greatly appreciated!
>
> Thanks,
>
> Joe Conway
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ken Corey | 2001-02-04 12:06:57 | Transactions in PLPGSQL? |
Previous Message | Tod McQuillin | 2001-02-04 07:59:03 | Re: Bug with rules in 7.0.3? |