>> There is idea to add trace event for every point at PSQL module which
>> was
>> recognized by parser as start of some statement (the line numbers available
>> at debug info\call stack).
>>
>
> I think these ideas should not mix concepts of trace with debug and
> profile. So for what it will be useful?
Trace *is* very useful for both debugging and profiling. Ask google for
"SQL Server
Profiler", btw. Ask people what they need...
I don't say that we don't need true debugger\profiler, no. But don't limit
trace
functionality artificially.
Regards,
Vlad
PS Please, don't start new useless flame. Thanks
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
