doesnt this force you to commit after every single DML statement?
From: Mercadante, Thomas F [EMAIL PROTECTED]
Date: 2003/12/15 Mon AM 08:36:09 EST
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
CC: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: RE: connection pooling from an application server
you to commit after every single DML statement?
From: Mercadante, Thomas F [EMAIL PROTECTED]
Date: 2003/12/15 Mon AM 08:36:09 EST
To: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
CC: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: RE: connection pooling from an application server to
oracle
]
Date: 2003/12/15 Mon AM 09:04:26 EST
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: RE: connection pooling from an application server to oracle
nope. the application server watches the connections and
transactions
the main problem is it's very hard to do a 10046
of list ORACLE-L [EMAIL PROTECTED]
Subject: Re: RE: connection pooling from an application server to
oracle
nope. the application server watches the connections and
transactions
the main problem is it's very hard to do a 10046 trace on a session
with connection pooling going
ORACLE-L [EMAIL PROTECTED]
Subject: Re: RE: connection pooling from an application server to oracle
nope. the application server watches the connections and
transactions
the main problem is it's very hard to do a 10046 trace on a session
with connection pooling going on, as a user
To: '[EMAIL PROTECTED]'
[EMAIL PROTECTED]
CC: '[EMAIL PROTECTED]' [EMAIL PROTECTED]
Subject: RE: connection pooling from an
application server to oracle
Ryan,
This is becoming for normal. There are a lot of
software pieces that do
connection pooling - basically, everybody is
plaing
