From: ow <oneway_111@yahoo.com>
To: Peter Childs <Blue.Dragon@blueyonder.co.uk>
To: pgsql-sql@postgresql.org
Subject: Re: A generic trigger?
Date: Sun, 14 Sep 2003 03:28:51 -0700 (PDT)
Message-ID: <20030914102851.82497.qmail@web21403.mail.yahoo.com> (raw)
In-Reply-To: <200309140926.50281.Blue.Dragon@blueyonder.co.uk>
--- Peter Childs <Blue.Dragon@blueyonder.co.uk> wrote:
> Yes it is possible and I've done it. The reason I'm not using it is because
> I
> wrote it in Pl/Python and if you attach the same trigger to more than one
> table in the same transaction pg/python (actually the entire server crashes
> but thats not the point) crashes. Well it did when I last tested it in early
> versions. I'm still thinking of getting around to rewriting it in a language
> without this bug, since nobody sounds like they are going to fix it. C might
> be best!
[snip]
Hi,
In my case, "company" and "company_backup" tables have the *same* structure, so
I was hoping for a simpler solution using just plpgsql.
Any ideas? Thanks
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
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: oneway_111@yahoo.com, Blue.Dragon@blueyonder.co.uk
Subject: Re: A generic trigger?
In-Reply-To: <20030914102851.82497.qmail@web21403.mail.yahoo.com>
* 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