that's an old bug that's been fixed. 0.7.1 is ancient you should upgrade to
0.7.10.
On Mar 17, 2013, at 1:38 AM, Warwick Prince warwi...@mushroomsys.com wrote:
Hi Michael
I have some fairly basic code which is moving data from one DB to another. I
have trapped errors on inserts just
specifically it occurs when you receive an exception on flush(), but then you
keep doing things that change the state of the session before calling
rollback(). here's the original test:
http://www.sqlalchemy.org/trac/attachment/ticket/2389/sqlalchemy_rollback_bug.py
On Mar 17, 2013, at 1:38
Cool - Thanks. Upgrade on the way.. :-)
Cheers
Warwick
specifically it occurs when you receive an exception on flush(), but then you
keep doing things that change the state of the session before calling
rollback(). here's the original test:
Hi Michael
I have some fairly basic code which is moving data from one DB to another.
I have trapped errors on inserts just in case there were unexpected
duplicates. When I go to commit this transaction, MySQL correctly throws
an IntegrityError exception: Duplicate Entry which I trap, and
