On Sep 20, 2010, at 3:51 PM, Randall Nortman wrote: > On Sep 19, 1:52 pm, Michael Bayer <mike...@zzzcomputing.com> wrote: >> On Sep 19, 2010, at 9:54 AM, Randall Nortman wrote: > [...] >> I think this is a bug in Pysqlite2. I can reproduce it with sqlite3 >> directly. > [...] >>> (I don't see where the spec says >>> that a DBAPI connection is always in a transaction.) >> >> Well, that you can't/shouldn't call "BEGIN" is implied by this paragraph, >> though weakly, but isn't specific about isolation. I also bet if you >> emailed the DB-SIG list, they'd be interested in this detail. > > The DB-SIG list agrees with you: > > http://mail.python.org/pipermail/db-sig/2010-September/005645.html > > And I have filed a bug on pysqlite: > > http://code.google.com/p/pysqlite/issues/detail?id=21
it seems a little dead on the pysqlite tracker, so I've reposted to bugs.python.org where things generally get very quick attention: http://bugs.python.org/issue9924 -- 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.
