Hi there, in one application I am using sqlalchemy 0.7.8 against Oracle
11 release 1 and I am hitting Oracle's lost contact more times than I
would like to. Since the app seems unable to recover from the error, I
have to restart it completely (it is a pyramid app).
According to this
On Dec 5, 2013, at 10:54 AM, Mariano Mara mariano.m...@gmail.com wrote:
Hi there, in one application I am using sqlalchemy 0.7.8 against Oracle 11
release 1 and I am hitting Oracle's lost contact more times than I would like
to. Since the app seems unable to recover from the error, I have
also note if you really want to prevent disconnects at the top of a
transaction, you can use a pessimistic approach, see
http://docs.sqlalchemy.org/en/rel_0_9/core/pooling.html?highlight=pessimistic#disconnect-handling-pessimistic
.
On Dec 5, 2013, at 11:05 AM, Michael Bayer
On jue 05 dic 2013 16:19:14 ART, Michael Bayer wrote:
also note if you really want to prevent disconnects at the top of a
transaction, you can use a pessimistic approach, see
http://docs.sqlalchemy.org/en/rel_0_9/core/pooling.html?highlight=pessimistic#disconnect-handling-pessimistic
.
