From: =?ISO-8859-15?Q?Torsten_Z=FChlsdorff?= <foo@meisterderspiele.de>
Subject: [Trigger] Help needed with NEW.* and TG_TABLE_NAME
Date: Tue, 11 May 2010 14:31:09 +0200
Organization: A noiseless patient Spider
Lines: 46
Message-ID: <hsbiuo$rbe$1@news.eternal-september.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 11 May 2010 12:35:36 +0000 (UTC)
Injection-Info: mx01.eternal-september.org;
	posting-host="AnkPUomeHXvuN7UdHvIkog";
	logging-data="28014"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19WK3fo41to1PhqKBjEHbn9"
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de;
	rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.5.0
Cancel-Lock: sha1:T3Yj2D2HvavRdMIKyStP2nn1rS8=
To: pgsql-sql@postgresql.org

Hello,

i have a problem with a trigger written in pl/pgsql.

It looks like this:

CREATE OR REPLACE FUNCTION versionize()
RETURNS TRIGGER
AS $$
BEGIN

   NEW.revision := addContentRevision (OLD.content_id, OLD.revision);

   /* not working line, just a stub:
   EXECUTE 'INSERT INTO ' || TG_TABLE_NAME  || ' SELECT $1 ' USING NEW;
   */

   RETURN NULL;

END;
$$ LANGUAGE 'plpgsql' VOLATILE;

The function should be used at different tables and is invoked before
UPDATEs. Everything what happens is the function call of
addContentRevision. After this call all data (with the updated revision
column) should be stored in the table as a new row.

My problem: the aim-table is not static. It's just always the table
which invoked the trigger. The trigger itself could be called at many
tables. I've tried some other ways of expressing the INSERT but nothing
worked:
- 'INSERT INTO ' || TG_TABLE_NAME  || ' SELECT NEW.*'
- INSERT INTO TG_TABLE_NAME SELECT NEW.*
- EXECUTE 'INSERT INTO ' || TG_TABLE_NAME  USING NEW;

Do you have any hints?

Greetings from Germany,
Torsten


-- 
http://www.dddbl.de - ein Datenbank-Layer, der die Arbeit mit 8 
verschiedenen Datenbanksystemen abstrahiert,
Queries von Applikationen trennt und automatisch die Query-Ergebnisse 
auswerten kann.