On 8/2/07, Bryan Pendleton <[EMAIL PROTECTED]> wrote:
> Is there any more information available about this method,
> such as:
> - when I would want to call it
> - what are the restrictions for when it is legal to call it
> - what affect it might have on connections that are active
Well, I suppose you know how connection pooling works. If normal
cases, you don't need this method at all. But it's suitable, when you
need to really close all connections (especially these on pool), i.e.
to perform some maintenance. As you can see, during normal run of
application you don't need it. But if your application is self-tuning,
self-living, self-whatever and has some "admin" part, you can need to
have disconnect to do something in db (i.e. recreate procedure, or do
physical copy (if used embedded server, with normal this isn't good
idea)).
You can call it on whetever place you want, but according to previous
text you probably feel, where you will call it. ;)
Active connections are closed 'cause are in pool too.
Is this enough for you?
--
Jiri {x2} Cincura (Microsoft Student Partner)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
