Subject | Re: Ackward trace information |
---|---|
Author | hvlad |
Post date | 2011-01-20T09:28:24Z |
--- In firebird-support@yahoogroups.com, Anderson Farias wrote:
Could you try with "log_statement_start enable" setting in trace configuration ?
Does firebird.log contains errors from trace plugin ?
Regards,
Vlad
> 2) I tested the one very simple statement that happens to *always* generate the 2 EXECUTE_STATEMENT_FINISH (normal folowed by FAILED) with FlameRobim:So, i should be able to reproduce it just using FlameRobin and SELECT * FROM anytable ?
>
> SELECT * FROM CONFIGURACAO
>
> AND there is no error! no exception! everything seems just normal, but... the second FAILED EXECUTE_STATEMENT_FINISH is always there!
Could you try with "log_statement_start enable" setting in trace configuration ?
> 3) During this and some other tests, I found out that the fb audit IS NOT writing every statements to the log file. Sometimes you execute statements that NEVER shows on audit log file -- it happened executing from the application, and from FlameRobin, on different ocasions! Sort of frustrating!Are you sure you not filtered out such statements using "exclude_filter" or "time_threshold" settings ?
Does firebird.log contains errors from trace plugin ?
Regards,
Vlad