From: | Franco Bruno Borghesi <franco(at)akyasociados(dot)com(dot)ar> |
---|---|
To: | Naeem Bari <naeem(dot)bari(at)agilissystems(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ON DELETE trigger blocks delete from my table |
Date: | 2004-10-25 19:33:33 |
Message-ID: | 1098732811.1995.5.camel@taz.oficina |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I've made a test case, and setting the trigger BEFORE DELETE doesn't
delete the rows from the table (but it does execute the trigger, and it
does insert the rows in the audit table), I dont' know why :(.
Anyway, setting the trigger AFTER DELETE works ok.
On Mon, 2004-10-25 at 15:56, Naeem Bari wrote:
> Hi,
>
>
>
> I am using postgres 7.4.5 on Redhat Enterprise Linux 3.
>
>
>
> My background is really on Oracle, and I am porting a largish database
> over to postgres.
>
>
>
> Here is my problem:
>
>
>
> On oracle, I had a table with an “on update or delete” trigger that
> copied the current row out to an audit table. Works like a champ. On
> postgres, when I try to delete a row, all it gives back to me is
> “DELETE 0” and does nothing.
>
>
>
> Here is the text of the trigger:
>
>
>
> ~~~~~~~~~~
>
> CREATE OR REPLACE FUNCTION public.func_job_status_upd()
>
> RETURNS trigger AS
>
> '
>
> begin
>
> insert into x_job_status values ( OLD.job_id,
> OLD.job_status_type_id, OLD.status_date, OLD.notes,
> OLD.edit_person_id, OLD.edit_date);
>
> return new;
>
> end;
>
> '
>
> LANGUAGE 'plpgsql' VOLATILE;
>
> ~~~~~~~~~~
>
>
>
> Any help would be appreciated!
>
>
>
> Thanks,
>
> naeem
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2004-10-25 19:45:19 | Re: The reasoning behind having several features outside |
Previous Message | Jeffrey Melloy | 2004-10-25 19:18:13 | Re: combining two queries? |