To make audit configuration changes known to the engine, Firebird must be restarted. On-demand interactive trace of some or all activity in some or all databases. An application which could be the fbtracemgr utility starts a user trace session, reads its output and shows traced events to the user in real time on the screen.
The user can suspend and resume the trace and, finally, stop it. Engine activity collection for a significant period of time a few hours or perhaps even a whole day for later analysis. An application starts a user trace session, reading the trace output regularly and saving it to one or more files.
The session must be stopped manually, by the same application or by another one. If multiple trace sessions are running, a listing can be requested in order to identify the session of interest. A new Trace API will provide a set of hooks which can be implemented as an external plug-in module to be called by the engine when any traced event happens. A plug-in will assume responsibility for logging such events in some custom way. However, since it will be changed in forthcoming sub-releases, it is not officially published and must be regarded as unstable.
Trace and Audit Services. Vlad Khorsun. Overview of Features. Tip Every trace session is assigned a unique session ID. The System Audit Session. Tip About the fbtrace. User Trace Sessions. Workings of a User Trace Session. Note Such files obviously do not live on the server. Tip The name of the character set of the attachment is included in any corresponding trace log records, placed between user:role and protocol:port , e. If someone changes it creates a trigger - handle errors as usual.
User application-side errors - user handling, server net, engine errors - server handling to the firebird. I think, it is quite fair. And you? Nice idea. Because to handle the bug one should be aware of it. You ask to conceal the bug and make developers oblivious to its existence. Then you ask developers "why didn't you fixed the bug that i didn't wanted you to know about". If you are sure you would write those triggers error-free, then why bother? Your log would be pristine no matter what the outcome of this ticket would be.
More so - that is their main reason d'etre. If application goes as normal i can make any clean-up in TDatabase. BeforeDisconnect event or like. Those triggers are server-side safety net warranting that cleanup would happen even when application or connection is defunct. Idea to report to application errors about unavailability of that application is but catch When programming with retvals it is natural and expected to check every statement for error explicitly.
When programming with exception it is natural to flow the statements and separate error interceptions. The question is what would be the sink for uncaught exception. It cannot be user application, since those triggers are designed to fire when the very existence of that application is no more given.
If some triggers can contain errors and this is important for you - yes, you should be aware of it. Skip to content. Please e-mail us what needs to be changed. To ensure quality, each change is checked by our editors and often tested on live Firebird databases , before it enters the main FAQ database. If you desire so, the changes will be credited to your name. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Where is the Firebird DB log file located in Windows? Ask Question. Asked 1 year, 3 months ago.
Active 1 year, 1 month ago. Viewed 2k times. I just installed Firebird 3.
0コメント