On Thu, Jan 9, 2014 at 9:59 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: > I do notice that you’re catching an IntegrityError. The typical pattern > when writing code that wants to catch these and then continue is to run the > individual set of questionable operations within a SAVEPOINT, that is a > begin_nested()/commit() block. Recent versions of SQLAlchemy have the > behavior such that when a flush() exception rolls back the SAVEPOINT, > objects that were not modified within the SAVEPOINT are not expired; only > those objects that changed within the save point’s scope do.
How recent does recent mean there? (just curious) -- 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.
