changelog in 0.8.0b1: http://docs.sqlalchemy.org/en/rel_0_9/changelog/changelog_08.html#change-1df6e3552ee895cd48952f95c0f0730a
ticket: http://www.sqlalchemy.org/trac/ticket/2452 I wonder if offering that the automatic rollback() on flush() might be optionally disabled (which means, a corrupted flush is in danger of being committed if the user is not careful) would be a compromise for this behavior in the bigger sense. On Jan 10, 2014, at 8:41 AM, Claudio Freire <klaussfre...@gmail.com> wrote: > 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
