non-intercepted eexceptions in on-disconnect trigger should be logged
---------------------------------------------------------------------
Key: CORE-3950
URL: http://tracker.firebirdsql.org/browse/CORE-3950
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Affects Versions: 2.5.1
Reporter: Dmitry
Currently, is database on-disconnect trigger fails, its autonomous transaction
is silently rolled back and disconnection proceeds like if no on-disconnect
trigger was present.
Apart from regular SQL statements or on-connect trigger, there is no standard
way to learn about that error.
Proposed enhancement - record the exception happened in on-disconnect trigger
into firebird.log, also dumping current_user, current_connection and perhaps
some more variables that may affect the trigger's behavior.
--
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
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
