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

Get EXCEPTION_MESSAGE and EXCEPTION_NUMBER when handling exceptions [CORE3254] #3622

Closed
firebird-automations opened this issue Nov 25, 2010 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @dyemanov

Duplicates CORE2040

Example:

when any do
begin
insert into error_log(error_code, error_message) values (EXCEPTION_NUMBER, EXCEPTION_MESSAGE);
exception;
end

For user exceptions EXCEPTION_NUMBER = RDB$EXCEPTION_NUMBER
For system (internal) exceptions EXCEPTION_NUMBER = 0, but EXCEPTION_MESSAGE must contain system message text (for example, EXCEPTION_MESSAGE = 'Division by zero', EXCEPTION_NUMBER = 0, SQLCODE = -802)

Will be helpful to have an ability to alter exception_number from CREATE and ALTER EXCEPTION commands.

====== Test Details ======

See functional\exception\handling_name_and_message.fbt

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

security: Managers [ 10013 ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue duplicates CORE2040 [ CORE2040 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Covered by another test(s)

Test Details: See functional\exception\handling_name_and_message.fbt

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