Jonathan: Yeah. That seems likely.
However, I feel "closer" to my database after removing zope.sqlalchemy from the mix. I guess I'm at a point where there is such a thing as too much abstraction. . ? BTW, I did give the nested tx a try, but as we both now know it did not work, and probably for the reasons you cited. That extra notification to the transaction manager would likely have done the trick. For me, right now, it is best to simply remove the zope stuff before the app gets too big. While I hate to go backward in time, I also like SQLA so much precisely because it gives me so much control. A fair trade-off to my way of thinking. Persistence matters, and that's why some people might read this. Thanks again. . . On Wednesday, June 28, 2017 at 3:10:28 PM UTC-6, Jonathan Vanasco wrote: > > > On Wednesday, June 28, 2017 at 4:28:32 PM UTC-4, Mike Bayer wrote: >> >> I'm not 100% sure that zope.sqlalchemy unconditionally emits COMMIT >> for the session that's associated. Though overall would need to see >> where you're getting request.session from and all that; if it's not >> associated with zope.sqlalchemy then you'd need to call >> session.commit() explicitly. >> > > rephrasing Mike's reply slightly... as I (think I) know what's wrong now... > > zope.sqlalchemy only knows that you did something with the session if you > use the ORM. you're using sqlalchemy core. > > you need to do this: > > > > from zope_sqlalchemy import mark_changed > mark_changed(session) > > > > That will let zop.sqlalchemy know that you did something in the session > and it will vote a COMMIT. otherwise it thinks you did nothing. > > -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.