I am still astonished about sqlite3 messing up transaction boundaries. And it is even worse than I thought because it breaks savepoints completely.
Have a look at this thread: http://mail.python.org/pipermail/python-list/2010-March/1239395.html Quote: Setting isolation_level=None is a must for anyone who want to do any serious work with sqlite. I tend to agree. Hope this stops somebody from running into the same problem. Greetings, Torsten -- DYNAmore Gesellschaft fuer Ingenieurdienstleistungen mbH Torsten Landschoff Office Dresden Tel: +49-(0)351-4519587 Fax: +49-(0)351-4519561 mailto:torsten.landsch...@dynamore.de http://www.dynamore.de Registration court: Mannheim, HRB: 109659, based in Karlsruhe, Managing director: Prof. Dr. K. Schweizerhof, Dipl.-Math. U. Franz -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@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.
