On Thursday, 9 January 2014 21:27:06 UTC, Michael Bayer wrote: > > > I think one of the error tracebacks (sorry, I lost them in other output) > mentioned autoflush - could the ORM be trying to flush bits of the > hierarchy before it's complete? Is there a better fix than removing the > nullable=False constraints? > > absolutely, which is why the “no_autoflush” contextmanager exists: > > > http://docs.sqlalchemy.org/en/rel_0_9/orm/session.html?highlight=no_autoflush#sqlalchemy.orm.session.Session.no_autoflush > > > the stack trace you’re getting will give you clues to where this context > manager should go. You’ll see the word “autoflush” in the stack trace, and > from there you can trace up to see the specific operation in your app that > is triggering it. > Thanks. That's exactly what I wanted :-)
Paul -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
