Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Jiri Cincura
On Thu, Dec 16, 2010 at 09:57, Thomas Steinmaurer wrote: > Or, I guess an exisiting connection with a given CURRENT_CONNECTION gets > re-used later on? Exactly. So you'll get later false messages. Not a good pattern for general usage. Anyway if somebody needs this and is aware of this behavior o

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Hernán Martínez
> On Wed, Nov 24, 2010 at 15:02, Jiri Cincura wrote: >> So any feedback is >> appreciated. > > Cool, no reply at all. > > http://blog.cincura.net/232218-trace-api-support-in-ado-net-provider-for-firebird-fbtrace/ Your post let me learn about the ADO.NET Trace API. Didn't know that such a thing

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Thomas Steinmaurer
> On Thu, Dec 16, 2010 at 09:50, Thomas Steinmaurer > wrote: >> Just speaking from the Trace API, you could start a trace session with >> the "connection_id" configuration parameter properly set. >> >> Just an idea. ;-) > > The problem would be connection pooling in .NET. :\ So, for an establis

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Jiri Cincura
On Thu, Dec 16, 2010 at 09:50, Thomas Steinmaurer wrote: > Just speaking from the Trace API, you could start a trace session with > the "connection_id" configuration parameter properly set. > > Just an idea. ;-) The problem would be connection pooling in .NET. :\ -- Jiri {x2} Cincura (x2develop

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Thomas Steinmaurer
> On Thu, Dec 16, 2010 at 09:02, Kjell Rilbe wrote: >> I would probably want to do this per connection. > > Not possible (directly) with current API. Just speaking from the Trace API, you could start a trace session with the "connection_id" configuration parameter properly set. Just an idea. ;

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Kjell Rilbe
Jiri Cincura skriver: > On Thu, Dec 16, 2010 at 09:02, Kjell Rilbe wrote: >> I would probably want to do this per connection. > > Not possible (directly) with current API. Is it possible to see in the trace output which connection was used for each statement? I guess I can accept to get "all" b

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Jiri Cincura
On Thu, Dec 16, 2010 at 09:02, Kjell Rilbe wrote: > I would probably want to do this per connection. Not possible (directly) with current API. -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer.com -

Re: [Firebird-net-provider] Trace API use cases

2010-12-16 Thread Kjell Rilbe
Jiri Cincura skriver: > if there's somebody using trace API from fbtracemgr or 3rd party > tools, can you share your scenarios, your goals, your usage, ...? I > implemented in .NET provider, but I'm now thinking how to do the > public classes etc. the best most useful way. So any feedback is > appr

Re: [Firebird-net-provider] Trace API use cases

2010-12-15 Thread Jiri Cincura
On Wed, Nov 24, 2010 at 15:02, Jiri Cincura wrote: > So any feedback is > appreciated. Cool, no reply at all. http://blog.cincura.net/232218-trace-api-support-in-ado-net-provider-for-firebird-fbtrace/ -- Jiri {x2} Cincura (x2develop.com founder) http://blog.cincura.net/ | http://www.ID3renamer

[Firebird-net-provider] Trace API use cases

2010-11-24 Thread Jiri Cincura
Hi *, if there's somebody using trace API from fbtracemgr or 3rd party tools, can you share your scenarios, your goals, your usage, ...? I implemented in .NET provider, but I'm now thinking how to do the public classes etc. the best most useful way. So any feedback is appreciated. -- Jiri {x2} C