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: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Harald Fuchs
> Sent: 2004. június 27. 12:12
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Trigger isn't fired
>
>
> In article <016601c45c14$136a9570$230a0a0a@compaq>,
> Együd Csaba <csegyud@vnet.hu> 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.
