From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Javier Fonseca V(dot)" <fonsecajavier(at)gmail(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Trigger Procedure Error: NEW used in query that is not in a rule |
Date: | 2007-08-11 08:16:47 |
Message-ID: | 162867790708110116h6825b5cj7a9f93a97f1328af@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
NEW is only plpgsql variable. It isn't visible on SQL level. You
cannot use new.*, you can:
execute 'INSERT ...' || 'VALUES(' || new.a || ',' || new.b ....
regards
Pavel
2007/8/11, Javier Fonseca V. <fonsecajavier(at)gmail(dot)com>:
>
>
> Hello.
>
> I'm doing a Trigger Procedure in pl/pgSQL. It makes some kind of auditing.
>
> I think that it's working alright except for the next line:
>
> EXECUTE 'INSERT INTO ' || quote_ident(somedynamictablename)
> || ' SELECT new.*';
>
> PostgreSQL keeps telling me: "ERROR: NEW used in query that is not in a
> rule". I think that this NEW problem is because of the scope of the EXECUTE
> statement (outside the scope of the trigger), so it doesn't recognize the
> NEW record.
>
> Maybe I could fix it concatenating column names and the 'new' values but I
> want to do my trigger as flexible as possible (I have several tables to
> audit).
>
> Somebody has any suggestion?
>
> Thanks a lot,
>
> Javier
From | Date | Subject | |
---|---|---|---|
Next Message | Louis-David Mitterrand | 2007-08-11 08:57:33 | Re: timestamp skew during 7.4 -> 8.2 upgrade |
Previous Message | Javier Fonseca V. | 2007-08-11 07:45:09 | Trigger Procedure Error: NEW used in query that is not in a rule |
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2007-08-11 09:06:44 | Re: Best Fit SQL query statement |
Previous Message | Javier Fonseca V. | 2007-08-11 07:45:09 | Trigger Procedure Error: NEW used in query that is not in a rule |