Thanks a lot for the inputs!
On Wednesday, December 9, 2020 at 9:08:51 PM UTC-7 Mike Bayer wrote:
> Oracle describes SessionPool at:
>
>
> https://cx-oracle.readthedocs.io/en/latest/user_guide/connection_handling.html#connpool
>
> This pool describes the connection lifecycle as first calling
>
Oracle describes SessionPool at:
https://cx-oracle.readthedocs.io/en/latest/user_guide/connection_handling.html#connpool
This pool describes the connection lifecycle as first calling pool.acquire(),
and then pool.release(connection), however the good news is that if
connection.close() is
I have tried below approach in SQLAlchemy 1.3.16.
Use a creator function - if you need to use special form when calling
cx_oracle.connect(), a creator function will allow you to plug into the
Engine how cx_oracle connections are established.
The creator function, that i associated would
Hi.
I would like to know how to use a cx-oracle SessionPool with SQLAlchemy.
We are leveraging the Session object of SQLAlchemy but we would like to use
the driver level pooling instead of SQLAlchemy pool.
Please advise.
Thanks,
Anupama
On Monday, October 3, 2011 at 12:23:58 PM UTC-6 Mike
Good afternoon,
We're using SQLAlchemy 0.6.6 and cx_Oracle 5.0.1, and our DBAs have
raised a concern about the number of sessions being kept open (where a
session is an Oracle concept, and a connection is on the socket).
We'd like to be able to keep the connection persistent, but we'd like
to be
This is a problem that would need to be solved mostly on the cx_oracle side,
then using standard SQLAlchemy APIs to implement.
Some googling didn't turn up a definitive answer if a single OCI connection can
persist, while its underlying session is killed. I found
On Oct 3, 2011, at 2:20 PM, Michael Bayer wrote:
3. Use pool events to emit commands when connections are checked out or
checked in. If you need to emit some SQL or cx_oracle commands on the DBAPI
connection upon checkout or checkin, the Engine provides pool events which
accomplish
