Triggered Data Change check

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Triggered Data Change check
Date: 2001-11-11 18:54:05
Message-ID: 20011111103631.D67544-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches


I wanted to know if there was a decision
to remove the triggered data change violation checks
from trigger.c or to change them to a per statement
check? I'm building a fix for some foreign key
problems, and want to cover some of those cases
in the regression test if we're going to allow it.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-11-11 19:14:38 Re: Triggered Data Change check
Previous Message Tom Lane 2001-11-11 16:57:07 Re: [COMMITTERS] pgsql/src/backend/postmaster postmaster.c

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2001-11-11 19:14:38 Re: Triggered Data Change check
Previous Message Tom Lane 2001-11-11 17:27:56 Re: Patch for Makefile race against current cvs