Comments below On Sep 27, 6:47 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Sep 27, 2009, at 4:11 AM, nkhalasi wrote: > in theory, you want to say session.flush() so that "n.next_id" is > persisted but the transaction is not committed. > > However the approach you have above wont work in any case assuming > the INSERT itself takes place within Session.flush() - the reentrant > call to flush should be raising an error immediately. maybe you're > on an older SQLA version that doesn't raise this assertion which is > why it chokes later on the double commits (which is again, an > assertion that something isnt being called in the proper sequence). >
Yes, flush() or commit() raises an error immediately. I am using 0.5.4 version of SQLAlchemy. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
