triggers (still more)
Thanks to the folks who gave me info on Unidata triggers. I've had
those
implemented for years and they do work very simply and well. Universe
has
been a whole different ballgame.
SNIPPED
Susan Joslyn
SJ+ Systems Associates, Inc.
PRC(r) Complete software development life-cycle
triggers (still more)
Hi everyone,
I have the triggers working - yay! Thanks Manu! - but now I'm to the
next
step, and of course stumbling again! My program sets a flag when it
wants
to disallow the write that called the trigger. The manual seems to
suggest
that I could use
-u2-
[EMAIL PROTECTED] De la part de Susan Joslyn
Envoyi : mardi 2 dicembre 2008 14:16
@ : u2-users@listserver.u2ug.org
Objet : Re: [U2] Universe triggers (still more)
Thanks to the folks who gave me info on Unidata triggers. I've had
those
implemented for years and they do work very
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
Sent: Wednesday, 3 December 2008 2:16 a.m.
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Universe triggers (still more)
Thanks to the folks who gave me info on Unidata triggers. I've had
those
implemented for years and they do work
Hi everyone,
I have the triggers working - yay! Thanks Manu! - but now I'm to the next
step, and of course stumbling again! My program sets a flag when it wants
to disallow the write that called the trigger. The manual seems to suggest
that I could use SetDiagnostic to fail this . but I'm
quote who='Susan Joslyn' date='Monday 01 December 2008'
Hi everyone,
I have the triggers working - yay! Thanks Manu! - but now I'm to the next
step, and of course stumbling again! My program sets a flag when it wants
to disallow the write that called the trigger. The manual seems to
Susan:
To expand further on Jeff's comment, the EXECSTAT variable is part of the
CALL arguements list. For instance, in UniData an update trigger might look
like:
001 SUBROUTINE U2.MASTER.TRIGGER.U ( ExecStat, DictFlag, atFILENAME, atID,
atRECORD )
The following table
Susan:
To expand further on Jeff's comment, the EXECSTAT variable is part of
the CALL arguements
list. For instance, in UniData an update trigger might look like:
001 SUBROUTINE U2.MASTER.TRIGGER.U ( ExecStat, DictFlag, atFILENAME, atID,
atRECORD )
The following table describes each
Setdiagnostics is a function which works by adding an error condition
message into the SQL error stack. A trigger program comes from the SQL
side of UV and runs within a transaction boundary, when the
setdiagnostics() function is used it will cause the trigger to go into
rollback mode on return
