Gaetano Mendola <[EMAIL PROTECTED]> 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 o
Neil Conway wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
I don't know how the check for the data integrity is implemented but if
is a trigger
It isn't -- trigger firing order is irrelevant to the original
question.
Well, it is. If the data integrity was done with a system trigger
created
Gaetano Mendola <[EMAIL PROTECTED]> writes:
> I don't know how the check for the data integrity is implemented but if
> is a trigger
It isn't -- trigger firing order is irrelevant to the original
question.
> 1) Create table
> 2) create a before insert trigger: trigger_a
> 3) create a before ins
On Mon, Nov 10, 2003 at 21:48:30 +0100,
Gaetano Mendola <[EMAIL PROTECTED]> wrote:
> Seems to me too, from the standard:
>
> "The order of execution of a set of triggers is ascending by value of
> their timestamp of creation in their
> descriptors, such that the oldest trigger executes first. I
Neil Conway wrote:
Thomas Erskine <[EMAIL PROTECTED]> writes:
A before trigger doesn't always fire. If a column being inserted into is
too small for the incoming data, psql complains:
ERROR: value too long for type ...
without giving the trigger procedure a chance to deal with it.
I belie
Thomas Erskine <[EMAIL PROTECTED]> writes:
> A before trigger doesn't always fire. If a column being inserted into is
> too small for the incoming data, psql complains:
> ERROR: value too long for type ...
> without giving the trigger procedure a chance to deal with it.
I believe this is a
POSTGRESQL BUG REPORT TEMPLATE
Your name : Thomas Erskine
Your email address : [EMAIL PROT
