Trigger isn't fired

[Együd Csaba]

Hi,
I created a trigger function and a trigger with that function on a table. It
is an "after insert or update or delete" trigger, in which I want to modify
a second table regardless of the current modifications.

Everything seems to be good on modifying the table, no error messages. After
the modifications the second table isn't modified at all. Should anybody
suggest me what I'm doing wrong? Does a trigger functon send error messages
if it fails?

My statements:
--------------
CREATE OR REPLACE FUNCTION trg_upd_prod_in stock() RETURNS trigger AS '
BEGIN
perform ''update t_products set
getup_instock=g et_stock_getup( ''||quote_liter al(NEW.producti d)||'',1) where
id=''||quote_li teral(NEW.produ ctid);
RETURN NEW;
END;
' LANGUAGE plpgsql;

GRANT ALL ON FUNCTION trg_upd_prod_in stock() TO public;

CREATE TRIGGER t_stockchanges_ trigger AFTER INSERT OR UPDATE OR DELETE ON
t_stockchanges
FOR EACH ROW EXECUTE PROCEDURE trg_upd_prod_in stock();

Many thanks,
-- Csaba Együd

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.707 / Virus Database: 463 - Release Date: 2004. 06. 15.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Stephan Szabo]

On Sat, 26 Jun 2004, [iso-8859-2] Együd Csaba wrote:

Hi,
I created a trigger function and a trigger with that function on a table. It
is an "after insert or update or delete" trigger, in which I want to modify
a second table regardless of the current modifications.

Everything seems to be good on modifying the table, no error messages. After
the modifications the second table isn't modified at all. Should anybody
suggest me what I'm doing wrong? Does a trigger functon send error messages
if it fails?

My statements:
--------------
CREATE OR REPLACE FUNCTION trg_upd_prod_in stock() RETURNS trigger AS '
BEGIN
perform ''update t_products set
getup_instock=g et_stock_getup( ''||quote_liter al(NEW.producti d)||'',1) where
id=''||quote_li teral(NEW.produ ctid);

I don't think this is going to do what you want. Are you sure you didn't
want EXECUTE rather than PERFORM?

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

[Együd Csaba]

Hi Stephan,
it was the problem, but not realy understand the reason. The documentetion
sais that perform doesn't porvide the return value and I thought I do not
need that. But I read absently, and didn't realized that the query to
perform must be a SELECT.

Thank you for opening my eyes. :) Now the trigger does its task. Thank you
very much.

Best regards,
-- Csaba Együd

-----Original Message-----
From: pg************* ****@postgresql .org
[mailto:pg****** ***********@pos tgresql.org]On Behalf Of Stephan Szabo
Sent: 2004. június 26. 22:32
To: Együd Csaba
Cc: Pg***********@P ostgresql.Org (E-mail)
Subject: Re: [GENERAL] Trigger isn't fired
On Sat, 26 Jun 2004, [iso-8859-2] Együd Csaba wrote:

Hi,
I created a trigger function and a trigger with that

function on a table. It

is an "after insert or update or delete" trigger, in which

I want to modify

a second table regardless of the current modifications.

Everything seems to be good on modifying the table, no

error messages. After

the modifications the second table isn't modified at all.

Should anybody

suggest me what I'm doing wrong? Does a trigger functon

send error messages

if it fails?

My statements:
--------------
CREATE OR REPLACE FUNCTION trg_upd_prod_in stock() RETURNS

trigger AS '

BEGIN
perform ''update t_products set

getup_instock=g et_stock_getup( ''||quote_liter al(NEW.producti d)
||'',1) where

id=''||quote_li teral(NEW.produ ctid);

I don't think this is going to do what you want. Are you
sure you didn't
want EXECUTE rather than PERFORM?

---------------------------(end of
broadcast)---------------------------
TIP 8: explain analyze is your friend

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.707 / Virus Database: 463 - Release Date: 2004. 06. 15.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.707 / Virus Database: 463 - Release Date: 2004. 06. 15.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postg resql.org so that your
message can get through to the mailing list cleanly

[Harald Fuchs]

In article <016601c45c14$1 36a9570$230a0a0 a@compaq>,
Együd Csaba <cs*****@vnet.h u> writes:

Hi Stephan,
it was the problem, but not realy understand the reason. The documentetion
sais that perform doesn't porvide the return value and I thought I do not
need that. But I read absently, and didn't realized that the query to
perform must be a SELECT. Thank you for opening my eyes. :) Now the trigger does its task.

Does it really? You're using NEW.productid, which should be undefined
for a DELETE trigger.
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Együd Csaba]

Yes, yes you are right. :)
I had already modified that (using TG_OP variable) before I posted the
letter just didn't mentioned.
By the way the trigger does its task. Rally. :)

Thanks,
-- Csaba

-----Original Message-----
From: pg************* ****@postgresql .org
[mailto:pg****** ***********@pos tgresql.org]On Behalf Of Harald Fuchs
Sent: 2004. június 27. 12:12
To: pg***********@p ostgresql.org
Subject: Re: [GENERAL] Trigger isn't fired
In article <016601c45c14$1 36a9570$230a0a0 a@compaq>,
Együd Csaba <cs*****@vnet.h u> writes:

Hi Stephan,
it was the problem, but not realy understand the reason.

The documentetion

sais that perform doesn't porvide the return value and I

thought I do not

need that. But I read absently, and didn't realized that

the query to

perform must be a SELECT.

Thank you for opening my eyes. :) Now the trigger does its task.

Does it really? You're using NEW.productid, which should be undefined
for a DELETE trigger.
---------------------------(end of
broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 2004. 06. 27.

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.712 / Virus Database: 468 - Release Date: 2004. 06. 27.

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend