суббота, 22 июня 2013 г., 8:26:58 UTC+3 пользователь werner написал:
On 22/06/2013 01:03, graf wrote:
sweep - sort of a garbage collector which removes unused versions of
transaction. There is Database header page information, where you can see
the the current transaction state, there
On Jun 22, 2013, at 10:19 AM, graf a.zhabotins...@gmail.com wrote:
суббота, 22 июня 2013 г., 8:26:58 UTC+3 пользователь werner написал:
On 22/06/2013 01:03, graf wrote:
sweep - sort of a garbage collector which removes unused versions of
transaction. There is Database header page
суббота, 22 июня 2013 г., 17:39:56 UTC+3 пользователь Michael Bayer написал:
On Jun 22, 2013, at 10:19 AM, graf a.zhabo...@gmail.com javascript:
wrote:
суббота, 22 июня 2013 г., 8:26:58 UTC+3 пользователь werner написал:
On 22/06/2013 01:03, graf wrote:
sweep - sort of a garbage
Hi Michael,
On 22/06/2013 16:39, Michael Bayer wrote:
...
def do_rollback(self, dbapi_connection):
# Use the retaining feature, that keeps the transaction going
dbapi_connection.rollback(True)
def do_commit(self, dbapi_connection):
# Use the retaining feature,
OK, issues I'd like either/both of you to deal with:
1. boolean for the rollback/commit - True or False by default? documentation
verbiage?
2. pull request to make the flag configurable at the dialect level
3. how backwards incompatible is this? if so, can be for 0.9 ?
On Jun 22, 2013,
please see http://www.sqlalchemy.org/trac/ticket/2763
On Jun 22, 2013, at 11:43 AM, Michael Bayer mike...@zzzcomputing.com wrote:
1. boolean for the rollback/commit - True or False by default?
documentation verbiage?
2. pull request to make the flag configurable at the dialect level
Looks good, thanks :)
суббота, 22 июня 2013 г., 18:44:21 UTC+3 пользователь Michael Bayer написал:
please see http://www.sqlalchemy.org/trac/ticket/2763
On Jun 22, 2013, at 11:43 AM, Michael Bayer
mik...@zzzcomputing.comjavascript:
wrote:
1. boolean for the rollback/commit - True or
четверг, 20 июня 2013 г., 21:52:37 UTC+3 пользователь Michael Bayer написал:
On Jun 18, 2013, at 6:09 PM, graf a.zhabo...@gmail.com javascript:
wrote:
I use SQLAlchemy inside Tornado, and I use a singleton to make the
Firebird connection inside application.
class
On Jun 21, 2013, at 4:42 PM, graf a.zhabotins...@gmail.com wrote:
Any way the problem is not related to singleton. As far as I understand the
Session creates the transaction after first commit/rollback/close and this
locks the Oldest transaction and after a while slow down the db speed.
sweep - sort of a garbage collector which removes unused versions of
transaction. There is Database header page information, where you can see the
the current transaction state, there are two parameters: Oldest transaction and
Next transaction. The range from Oldest to Next - is the versions of
On Jun 21, 2013, at 7:03 PM, graf a.zhabotins...@gmail.com wrote:
sweep - sort of a garbage collector which removes unused versions of
transaction. There is Database header page information, where you can see the
the current transaction state, there are two parameters: Oldest transaction
On 22/06/2013 01:03, graf wrote:
sweep - sort of a garbage collector which removes unused versions of transaction. There
is Database header page information, where you can see the the current transaction state,
there are two parameters: Oldest transaction and Next transaction. The range from
On Jun 18, 2013, at 6:09 PM, graf a.zhabotins...@gmail.com wrote:
I use SQLAlchemy inside Tornado, and I use a singleton to make the Firebird
connection inside application.
class FirebirdDatabase(object):
def __init__(self, firebird_params, echo=False):
engine =
I use SQLAlchemy inside Tornado, and I use a singleton to make the Firebird
connection inside application.
class FirebirdDatabase(object):
def __init__(self, firebird_params, echo=False):
engine =
create_engine('firebird+fdb://%(user)s:%(password)s@%(host)s:%(port)s/%(path)s'
%
14 matches
Mail list logo
