Peter Childs <[EMAIL PROTECTED]> writes:
> 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 po
--- Peter Childs <[EMAIL PROTECTED]> 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 that
On Sunday 14 September 2003 02:13, ow wrote:
> Hi,
>
> Am looking for a way to minimize the amount of fuctions that support
> triggers. E.g., there's "company" and "company_backup" tables. Update
> trigger on the "company" table will put a record in the "company_backup"
> table whenever "company" r
Hi,
Am looking for a way to minimize the amount of fuctions that support triggers.
E.g., there's "company" and "company_backup" tables. Update trigger on the
"company" table will put a record in the "company_backup" table whenever
"company" record is updated.
The problem is that there's quite a f
