Subject | Re: [firebird-support] about threads |
---|---|
Author | Thomas Steinmaurer |
Post date | 2008-03-16T09:34:53Z |
Matt,
a read-only read committed one).
But, connection pool implementation usually have some kind of timeout
parameter which closes a physical connection in the pool after a period
of idle time.
--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
> Anderson Farias schrieb:If there is an active transaction involved, then for sure (if it is not
>> BUT, you can always use a database connection pool, that should speed up
>> things (connecting to db), and you don't even need to code your own, you can
>> use IBConnectionBroker that comes with IBX.
>
> Some time ago, I had built such a connection pool myself (create/open a
> connection when needed, reuse it somewhen later, and let it exist - and
> open! - until program termination). It does work, but deep inside I have
> kind of a "bad feeling" - doesn't it really "hurt" FB if a database
> connection remains open for a looong time, for example, some weeks
> or even months?
a read-only read committed one).
But, connection pool implementation usually have some kind of timeout
parameter which closes a physical connection in the pool after a period
of idle time.
--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com