Trigger which fires on commit? (Multi-table intergrity constraint)

From: Stephane Bortzmeyer <bortzmeyer(at)nic(dot)fr>
To: pgsql-general(at)postgresql(dot)org
Subject: Trigger which fires on commit? (Multi-table intergrity constraint)
Date: 2002-08-08 08:22:41
Message-ID: 20020808082241.GA3059@nic.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

[Question already asked but may be badly explained. I rephrase it.]

I have several tables and an integrity constraint which spans several
tables (for an Internet registry, a table Domains, a table Hosts and a
table Nameservers which links them: a Domain needs >= 2
nameservers). The tables are updated in the same transaction and I
want the database to be OK after the commit.

I can check many things from triggers but apparently triggers can only
be fired for a statement (like INSERT), not for a whole transaction.

Oracle supports ON COMMIT triggers and they solve nicely this
problem. But apparently PostgreSQL does not. Any idea?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stephane Bortzmeyer 2002-08-08 08:26:02 Re: "history" key in pgsql
Previous Message Alex Cheung Tin Ka 2002-08-08 08:15:33 "history" key in pgsql