Hi Clay, On Wed, 2011-04-27 at 11:21 -0700, Clay Gerrard wrote:
> ... and all connections would automatically issue the correct begin > statement and acquire a reserved lock at the beginning of the > transaction. But as it is, they don't do anything until they get down > to the update, and it's kind of a disaster. I had this disaster a number of times as well. For that reason I created a patch for this issue http://bugs.python.org/issue10740 That change makes the time when pysqlite starts a transaction configurable. The obvious approach to start a transaction on each command breaks "pragma foreign_keys=on" since it has to be used outside a transaction. I welcome comments and suggestions about that patch. 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 sqlalchemy@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.
