First of all thanks to you I have been using it extensively in our production environment, and it has proven to be a very valuable tool
I frequently utilize the TransactWrite class for handling transactions.
However, I recently encountered an issue where, after invoking the _commit method, the transaction does not appear to flush the last items as expected. This behavior seems to cause problems when sharing the Connection object across different operations
Could you please clarify whether this is the intended behavior or if it might be a bug?
cf
pynamodb Transaction
class Transaction:
"""
Base class for a type of transaction operation
"""
def __init__(self, connection: Connection, return_consumed_capacity: Optional[str] = None) -> None:
self._connection = connection
self._return_consumed_capacity = return_consumed_capacity
def _commit(self):
raise NotImplementedError()
def __enter__(self: _TTransaction) -> _TTransaction:
return self
def __exit__(self, exc_type, exc_val, exc_tb):
if exc_type is None and exc_val is None and exc_tb is None:
self._commit()
# i think if the _commit is succeded the transcation item should be flushed
First of all thanks to you I have been using it extensively in our production environment, and it has proven to be a very valuable tool
I frequently utilize the TransactWrite class for handling transactions.
However, I recently encountered an issue where, after invoking the _commit method, the transaction does not appear to flush the last items as expected. This behavior seems to cause problems when sharing the Connection object across different operations
Could you please clarify whether this is the intended behavior or if it might be a bug?
cf
pynamodb Transaction
pynamodb TransactWrite code
def b(): with transaction as tx:
do something