-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
TRACE: add ability for logging ERRORs that occur in runtime (lock conflicts, PK/UK/FK violations et al) [CORE3539] #3896
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladFix Version: 2.5.2 [ 10450 ] Fix Version: 3.0 Alpha 1 [ 10331 ] Component: Engine [ 10000 ] |
Commented by: @hvlad The feature is committed into v2.5.2 and will be ported forward into v3. New trace configuration parameter is added : "log_errors". It could be used in both <database> and <services> sections. 2012-05-03T00:02:59.9390 (3324:0000000002D0A410) UNAUTHORIZED ATTACH_DATABASE 2012-05-03T00:02:59.9390 (3324:0000000002D0A410) ERROR AT jrd8_attach_database or 2012-05-03T00:04:16.4080 (3324:0000000002D0A410) ERROR AT jrd8_fetch There are two new trace events : "ERROR" and "WARNING" followed by API entrypoint name which returns error. Transaction (statement) is not reported as part of "ERROR" and "WARNING" events as there could be no |
Modified by: @cincuranet |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @pavel-zotov
Replaces CORE3334
Relate to DNET463
sibj.
Commits: d78703c 1bcb480
The text was updated successfully, but these errors were encountered: