Thanks for the help. I discovered my error while coming up with a better example.
Thanks,
Dmitri"A.Bhuvaneswaran" <[EMAIL PROTECTED]> wrote:
> Why dont you try to write your trigger in C?Hi, one cannot write triggered procedures in C. Currently, it can only bewritten in plpsgql.> > CREATE
"A.Bhuvaneswaran" <[EMAIL PROTECTED]> writes:
>> Why dont you try to write your trigger in C?
> Hi, one cannot write triggered procedures in C.
Oh? All the built-in trigger procedures are.
regards, tom lane
---(end of broadcast)--
On Mon, 20 Oct 2003, A.Bhuvaneswaran wrote:
> > Why dont you try to write your trigger in C?
>
> Hi, one cannot write triggered procedures in C. Currently, it can only be
> written in plpsgql.
Where did you get that impression from?
Do an
SELECT tgrelid,tgfoid,proname from pg_trigger,pg_proc wh
> Why dont you try to write your trigger in C?
Hi, one cannot write triggered procedures in C. Currently, it can only be
written in plpsgql.
> > CREATE FUNCTION "public"."check_shipment" () RETURNS trigger AS'
> > begin
> > If new.shipment_type_id = 4 then
> > --do something
> > e
Why dont you try to write your trigger in C?
On Mon, 20 Oct 2003, Dmitri Fuerle wrote:
>
>I'm writing a trigger but running into problems. My problem is that I can not
> determine anyway to tell what fields are in the *new* record. Without knowing what
> fields are there I get runtime e
I'm writing a trigger but running into problems. My problem is that I can not determine anyway to tell what fields are in the *new* record. Without knowing what fields are there I get runtime errors if that's not what is being updated example:
CREATE FUNCTION "public"."check_shipment" ()
