I have a DLL which constructs an array of Database / Transaction Pairs. When a user requires information from the database, the application requests a connection from the DLL for which the request gets it's own database / transaction pair. When the application is finished with the request it hands the pair back off to the DLL which then "Commits" the transaction and marks the pair available for another request.


----- Original Message ----
From: Helen Borrie <helebor@...>
To: firebird-support@yahoogroups.com
Sent: Sunday, June 10, 2007 3:33:39 AM
Subject: Re: [firebird-support] Idle Connection / Cache Release

At 09:18 AM 10/06/2007, you wrote:

>Let me clarify some more...
>
>I am using connection pooling and each connection "commits" after a
>user is done with a session, but the DB connection remains open and
>ready for the next user.

How are you doing that?

./heLen



[Non-text portions of this message have been removed]