Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add built-in context variables 'PROC_NAME' and 'ERROR_LINE' and database level trigger that fires on any ERROR [CORE3587] #3941

Open
firebird-automations opened this issue Aug 29, 2011 · 0 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pavel-zotov

Votes: 2

Currently there is no way to obtain the point of stored procedure that faults (i.e. when error occurs in some sp "A" we can not see on *server* side what exact statement lead to error). Consequently we can not to automate such task as logging of errors by SERVER program units.

I think that introducing of two new context variables will be useful. These variables should store the name of currently executing SP and the LINE of currently executed statement in this SP.
In such case if we had DB-level trigger that fires on any error the task of PRECISE logging could be done easy (by call in autonomous transaction INSERT INTO T_LOG ... from this trigger; no need to write thousands WHEN-handlers in each SP).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant