Re: [Sqlalchemy-tickets] [sqlalchemy] #2864: Disconnect via IDLE_TIME resource limit not handled by
Brought to you by:
zzzeek
|
From: sqlalchemy <mi...@zz...> - 2013-11-14 18:35:29
|
#2864: Disconnect via IDLE_TIME resource limit not handled by SQLAlchemy
---------------------------+-----------------------------------
Reporter: Bluehorn | Owner: zzzeek
Type: defect | Status: new
Priority: medium | Milestone: 0.8.xx
Component: oracle | Severity: trivial - <10 minutes
Resolution: | Keywords:
Progress State: in queue |
---------------------------+-----------------------------------
Comment (by Bluehorn):
Replying to [comment:4 zzzeek]:
> this could be improved if is_disconnect also gave out info regarding
"try to close" or not, then we'd have to get that all into the pool logic
and such, not sure if I'm eager to get into that as the pool's stability
is pretty critical.
I would try to improve the Oracle dialect class to check if the connection
is still alive before trying to close it. I did not find any method in
cx_Oracle to check that though. Perhaps later :)
--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2864#comment:5>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python
|