On Sun, Nov 25, 2018 at 12:55 PM Chris Withers <ch...@withers.org> wrote:
> > > So....at the moment you can still say this: > > > > > > with session.transaction: > > > > > > which will do the commit and rollback but not the close(). > > > > Potentially silly question: when is it useful to commit the session but > > not close it? the Session is maintaining the scopes of many different objects, which are, a Connection, a transaction, and all the objects you're deailng with. It's pretty common folks want to commit their transaction and then afterward keep working with all the objects they have attached to the session to load more data or commit more changes. > > Still curious about this, gues I could RTSL or find the bit of the > manual, but I'd prefer to not misinterpret either! > > cheers, > > Chris -- 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.
