You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
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.
The parameter could have boolean value "true" or "false" (default). If "log_errors"set to "true" every time user status-vector
contains error or warning corresponding event will be placed into the trace output, for example :
2012-05-03T00:02:59.9390 (3324:0000000002D0A410) ERROR AT jrd8_attach_database
TEST.FDB (ATT_0, SYSDBA, WIN1251, XNET:W2K3-X64)
335544472 : Your user name and password are not defined. Ask your database administrator to set up a Firebird login.
2012-05-03T00:04:16.4080 (3324:0000000002D0A410) ERROR AT jrd8_fetch
TEST.FDB (ATT_11, SYSDBA:NONE, WIN1251, XNET:W2K3-X64)
335544321 : arithmetic exception, numeric overflow, or string truncation
335544778 : Integer divide by zero. The code attempted to divide an integer value by an integer divisor of zero.
There are two new trace events : "ERROR" and "WARNING" followed by API entrypoint name which returns error.
Since tracing performed inside the engine (not inside y-valve or network listener) there will be "jrd8_XXX"
entrypoints names reported, not "isc_XXX" equivalents as could be expected.
Transaction (statement) is not reported as part of "ERROR" and "WARNING" events as there could be no
transaction (statement) active at the point where error is catched. Database attachment or service connection
information is reported however.