Jim Carroll added the comment:
Completely understood.
I recently found a workaround. Setting isolation_level to None seems to
mitigate the issue, ie:
db = sq.connect(':memory:', isolation_level=None)
I'm hoping to put some time in scrutinizing the c-api code later this week (as
SQLite bugs directly affect projects we work on) to see if we can get to the
bottom of the issue.
----------
title: sqlite3 COMMIT nested in SELECT returns unexpected results ->
sqlite3 COMMIT nested in SELECT returns unexpected results
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue23129>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
