From: | ow <oneway_111(at)yahoo(dot)com> |
---|---|
To: | Peter Childs <Blue(dot)Dragon(at)blueyonder(dot)co(dot)uk>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: A generic trigger? |
Date: | 2003-09-14 10:28:51 |
Message-ID: | 20030914102851.82497.qmail@web21403.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
--- Peter Childs <Blue(dot)Dragon(at)blueyonder(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Rudi Starcevic | 2003-09-14 11:24:37 | Linked Lists example. |
Previous Message | Peter Childs | 2003-09-14 08:26:50 | Re: A generic trigger? |