Determine if trigger is being fired as a result of a CASCADE or direct user
command
-----------------------------------------------------------------------------------
Key: CORE-4348
URL: http://tracker.firebirdsql.org/browse/CORE-4348
Project: Firebird Core
Issue Type: New Feature
Reporter: Tim Kelly
It would be very useful to be able to determine within a trigger if the trigger
is being fired as a result of a cascaded update/delete/setnull or directly by
the end user.
Perhaps this could be done by setting a flag that can be checked within the
trigger code.
Alternatively, another solution would be to introduce new <single action>'s so
that specialized triggers could be run / not run in the event of a cascade:
eg:
CREATE TRIGGER...
<single_action> ::= INSERT | UPDATE | DELETE
becomes:
<single_action> ::= INSERT | UPDATE | DELETE | [NOT] CASCADE_UPDATE | [NOT]
CASCADE_DELETE | [NOT] CASCADE_SET_NULL
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
