From: Horst Herb <hherb@malleenet.net.au>
To: Jeff Eckermann <jeckermann@verio.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: how to use record type
Date: Sun, 19 Aug 2001 23:20:06 +1000
Message-ID: <01081923200626.01835@munin.gnumed.dhs.org> (raw)
In-Reply-To: <009401c12727$71b3a150$279c10ac@INTERNAL>
References: <0108170824511W.01835@munin.gnumed.dhs.org>
<009401c12727$71b3a150$279c10ac@INTERNAL>
On Saturday 18 August 2001 00:18, you wrote:
> I have encountered this problem (in a different context), and could not
> find a way to insert entire rows/records in the way that you appear to
> want. But it worked fine if I INSERTed explicitly, like:
> INSERT INTO table VALUES (OLD.field1, OLD.field2, ..., OLD.fieldn);
> That should work fine inside a plpgsql function.
This is what I have been doing until recently. Rather ugly, as it is >250
different tables which need this. Meaning that I had to manually write the
trigger functions for each table, attribute by attribute.
At present, I solved the situation like that:
- all tables that need the trigger function inherit a parent table
- a python script scans all tables inheriting the parent table and then
generates the trigger functions for them. I still execute the script manually
after updating or inserting tables.
- now I am trying to find out how to implement a trigger on the system tables
that will fire my Python script automatically whenever a table inheriting
this special parent table is altered or created.
Sad that such an ugly hack is neccessary though.
Horst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: hherb@malleenet.net.au, jeckermann@verio.net
Subject: Re: how to use record type
In-Reply-To: <01081923200626.01835@munin.gnumed.dhs.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox