Skip site navigation (1) Skip section navigation (2)

Re: before trigger doesn't, on insert of too long data

From: Neil Conway <neilc(at)samurai(dot)com>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: before trigger doesn't, on insert of too long data
Date: 2003-11-11 02:47:53
Message-ID: 87llqnwrhi.fsf@mailbox.samurai.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Gaetano Mendola <mendola(at)bigfoot(dot)com> writes:
> Well, it is. If the data integrity was done with a system trigger
> created at table creation time the firing order is relevant.

Right, but the data integrity check is _not_ done via a system
trigger. Hence, "trigger firing order is irrelevant to the original
question", as I said earlier.

> Good to hear. So, why the standard is there ?

According to the docs, "PostgreSQL development tends to aim for
conformance with the latest official version of the standard where
such conformance does not contradict traditional features or common
sense." The previous consensus seemed to be that being non-conformant
with the standard in this area was worth it.

I'm not particularly attached to the current behavior though, so feel
free to restate your case for changing the trigger firing order on
-bugs.

-Neil


In response to

pgsql-bugs by date

Next:From: SHADOWPLAY - Dave AdamsDate: 2003-11-11 06:15:38
Subject: Selecting from a VIEW is NOT optimized like a similar SELECT statement
Previous:From: Gaetano MendolaDate: 2003-11-11 02:17:00
Subject: Re: before trigger doesn't, on insert of too long data

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group