Re: [Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Jiri Cincura
On Tue, May 4, 2010 at 19:57, Ivan Arabadzhiev wrote: > but I just though I should ask if > any other deallocation should take place. If the command is inside using, you're safe. > The server firebird server hasn`t crashed in more than an year, and I > don`t reboot, so I assume if resources are

Re: [Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Ivan Arabadzhiev
Tue, 04 May 2010 20:44:51 +0300, Jiri Cincura : > On Tue, May 4, 2010 at 15:25, Ivan Arabadzhiev > wrote: >> So having inactive queries a few hours after their transactions have >> ended >> does not mean I messed up? :) > > Not necessarily. > Ok, so the reason I asked in the first place was th

Re: [Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Jiri Cincura
On Tue, May 4, 2010 at 15:25, Ivan Arabadzhiev wrote: > So having inactive queries a few hours after their transactions have ended > does not mean I messed up? :) Not necessarily. -- Jiri {x2} Cincura (CTO x2develop.com) http://blog.cincura.net/ | http://www.ID3renamer.com

Re: [Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Ivan Arabadzhiev
Tue, 04 May 2010 16:21:14 +0300, Jiri Cincura : > On Tue, May 4, 2010 at 13:51, Ivan Arabadzhiev > wrote: >> Or is that table expected to show inactive querys (a history of some >> sort)? > > It's a stable snapshot of time when issued. Also note whether the > query is active or not. > So having

Re: [Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Jiri Cincura
On Tue, May 4, 2010 at 13:51, Ivan Arabadzhiev wrote: > Or is that table expected to show inactive querys (a history of some > sort)? It's a stable snapshot of time when issued. Also note whether the query is active or not. -- Jiri {x2} Cincura (CTO x2develop.com) http://blog.cincura.net/ | htt

[Firebird-net-provider] Should statements be "freed"?

2010-05-04 Thread Ivan Arabadzhiev
I am looking through a database of mine and can`t help noticing that MON$STATEMENTS contains thing which should be done with a long time ago. I don`t use fbcommand outside of "using(){}" but should anything else be done? Or is that table expected to show inactive querys (a history of some sor