>
>
> It's possible that if you're using the session in "autocommit" mode and
> just want to occasionally "broadcast" your object state to a quick
> "flush everything", that in fact turning off the "accounting" feature
> with this flag is appropriate. I'm looking at this code and it really
On 01/20/2017 04:25 PM, Philip Scott wrote:
Hi Mike
Thank you for your quick and thoughtful response as usual!
so the quick and dirty approach is a flag I'm not enthused about,
nevertheless I don't plan on removing, called
_enable_transaction_accounting,
Yes I saw this when
Hi Mike
Thank you for your quick and thoughtful response as usual!
> so the quick and dirty approach is a flag I'm not enthused about,
> nevertheless I don't plan on removing, called
> _enable_transaction_accounting,
>
Yes I saw this when poking around in the source code - it does seem like
On 01/20/2017 01:45 PM, Philip Scott wrote:
Hello all,
Short summary of my question:
Is it possible to stop rollback() from expiring dirty objects?
Specifically, in the case where there are
- local changes made outside to mapped objects outside of a transaction
- flush() is called
- the
Hello all,
Short summary of my question:
Is it possible to stop rollback() from expiring dirty objects?
Specifically, in the case where there are
- local changes made outside to mapped objects outside of a transaction
- flush() is called
- the flush fails
In this case SQLAlchemy will
