On Tue, Aug 16, 2011 at 3:59 PM, Dirk Makowski <dirk.makow...@googlemail.com > wrote:
> Excellent, Mike, thanks. > > This solves my 2nd post, and there's also an equivalent for update. So I > can use > sess.query(Role).filter(Role.**id==id).update(values, > synchronize_session=False) > where I previously had loaded the entity and then updated it. > > Fine, because I am using the ORM again, the problem in post 1 is > alleviated. Nonetheless I am still curious about that phenomenon. > > Dirk > > Looking at the limited snippet in the first post, it seems that the commit should be sess.commit() where does "transaction" come from? -- Mike Conley -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.