Thanks Mike. That approach is working well.
On Sunday, 15 January 2017 03:48:19 UTC+11, Mike Bayer wrote:
>
>
>
> On 01/13/2017 11:13 PM, Stephen Davies wrote:
> > (Using latest SqlAlchemy with either sqlite or postgres on a Flask
> server)
> >
> > I have a table of entities and stats with
a given application makes explicit use of `commit` and `rollback` on the
sqlalchemy session.
a few views require interaction with some other technologies via a
two-phase commit.
under the current design, i can't enable two-phase commits for everything.
i'm not sure I can detect the need
>
>
> 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
