Cédric Krier
36aa3a5aed
When a connection in the pool is disconnected, it stays in the pool and it may still be served. Using such connection raise an OperationalError and so the request is retried but before that the connection is put back to the pool. So we may get it back again. It is not possible to distinct between an OperationalError due to a disconnection or due to a isolation error for example. So with the current design of Transaction API, an OperationalError always put back the connection to the pool. This main that we can only ensure that the connections served are still connected by executing a simple query. And close connections that are failing. Closes #12452 (grafted from f8aaf62a0c7508e3f3398e47dc2b86e6f8f06cc0) --HG-- branch : 6.0
This repository contains all the packages of Tryton.
To have symlinks for modules created automatically on Mercurial update, add
the following line to the hooks section of your .hg/hgrc:
update.modules = .hooks/link_modules
To automatically generate requirements files on Mercurial update, add
the following line to the hooks section of your .hg/hgrc:
update.requirements = .hooks/update_requirements
.. warning::
The process of updating requirements files may take some time
Then you can install the required dependencies with:
pip install -r requirements.txt
And you can also install the development dependencies with:
pip install -r requirements-dev.txt