Oliver Jowett wrote:
> Kevin Grittner wrote:
>
>> Wading through loglevel=2 output today, it occurred to me that it would
>> be nice if the jdbc log file included a prefix with something to
>> identify the connection. Sometimes you can only get an error to occur
>> on a busy system with multiple active connections, and the jdbc log
>> currently mixes everything together, which can make it hard to follow.
>
>
> Yes, this is on my todo list..
>
> The simplest way to do it seems to be to just have a static driver-wide
> counter to assign IDs to connections.
I just committed something like this to CVS HEAD -- loglevel is now
handled per connection (previously it was effectively driver-wide,
despite being specified as part of the connection URL), and logging
output now has both a connection ID and timestamp on each line.
-O
