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.Dismiss alert
2017-02-02T10:47:58.9080 (23764:00F3BFD8) WARNING AT jrd8_prepare
...
335544807 : SQL warning code = 301
335544808 : DATE data type is now called TIMESTAMP
3) errors which actually can not be fixed by application developer or DBA:
Submitted by: @pavel-zotov
Replaces CORE4486
It will be GREAT if one may to filter out following messages from trace:
1) info:
2017-02-02T10:45:57.9130 (31572:00F1BFD8) TRACE_INIT
SESSION_2
2017-02-02T10:45:57.9130 (31572:00F1BFD8) TRACE_FINI
SESSION_2
2) warnings:
2017-02-02T10:47:58.9080 (23764:00F3BFD8) WARNING AT jrd8_prepare
...
335544807 : SQL warning code = 301
335544808 : DATE data type is now called TIMESTAMP
3) errors which actually can not be fixed by application developer or DBA:
2017-02-02T10:46:24.2150 (16216:00FABFD8) ERROR AT jrd8_fetch
some_production (ATT_3103928, QWERTY:MANAGER, WIN1251, TCPv4:192.168.1.1)
335544364 : request synchronization error
Trace config could contain smth like:
log_info = true | false
log_warnings = true | false
...
Commits: 035d008 370572b 800baa6
The text was updated successfully, but these errors were encountered: