Re: [sqlalchemy] Re: ORA-03135 and SqlAlchemy... Is there a design pattern to get around this?

the pessimistic disconnect logic will help you in dealing with connections that are stale, such as if the database was restarted, and you'd like to ensure new connections from the pool are always live. However, if you are getting these 3135 errors in the middle of inserting a BLOB or something

[sqlalchemy] Re: ORA-03135 and SqlAlchemy... Is there a design pattern to get around this?

Thanks Jonathan - I'll take a look On Monday, 9 July 2018 22:09:57 UTC+1, Jonathan Vanasco wrote: > > http://docs.sqlalchemy.org/en/latest/core/pooling.html > > specifically: > > http://docs.sqlalchemy.org/en/latest/core/pooling.html#disconnect-handling-pessimistic > and > >

[sqlalchemy] Re: ORA-03135 and SqlAlchemy... Is there a design pattern to get around this?

http://docs.sqlalchemy.org/en/latest/core/pooling.html specifically: http://docs.sqlalchemy.org/en/latest/core/pooling.html#disconnect-handling-pessimistic and http://docs.sqlalchemy.org/en/latest/core/pooling.html#custom-legacy-pessimistic-ping There is also:

[sqlalchemy] ORA-03135 and SqlAlchemy... Is there a design pattern to get around this?

Hi. We've recently ported a database to an Amazon cloud based instance.. Sporadically I am getting ORA-3135 errors. >From what I can tell here there may be some configuration parameters