So you are saying that one cannot do more than one transaction with a
connection. Surely commit/rollback is a separate matter from saying, 'I
have finished with this connections, now let someone else use it'?
Of course, I can close the connection, which will force the pool manager to
create a new one, but that is not what I am after.
|---------+---------------------------->
| | "Thomas Fischer" |
| | <[EMAIL PROTECTED]|
| | u.net> |
| | |
| | |
| | 27-Aug-2004 10:28|
| | Please respond to|
| | "Apache Torque |
| | Users List" |
| | <[EMAIL PROTECTED]|
| | pache.org> |
| | |
|---------+---------------------------->
>-------------------------------------------------------------------------------------------------------------------------|
|
|
|
|
|
|
| To: "Apache Torque Users List" <[EMAIL PROTECTED]>
|
|
|
| cc:
|
| Subject: Antwort: Releasing DB connections
|
>-------------------------------------------------------------------------------------------------------------------------|
Hi,
personally I use Transaction.begin() to get a connection and
Transaction.commit(connection) , transaction.rollback(connection) or
transaction.safeRollback(connection) to give it back to the pool.
Thomas
[EMAIL PROTECTED] schrieb am 27.08.2004 10:21:11:
> A bit of clarification please.
>
> One uses torque.getConnection to get a DB connection from the pool. How
and
> when is it returned to the pool?
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
