[issue10513] sqlite3.InterfaceError after commit

Erlend E. Aasland added the comment: Closing as fixed. If someone disagrees; please re-open. -- resolution: -> fixed status: pending -> closed ___ Python tracker ___

[issue10513] sqlite3.InterfaceError after commit

Erlend E. Aasland added the comment: I cannot reproduce this with Python 3.8, 3.9, nor 3.10 (macOS builds from python.org). Suggesting to close this. -- nosy: +erlendaasland status: open -> pending ___ Python tracker

[issue10513] sqlite3.InterfaceError after commit

Roundup Robot added the comment: New changeset 74a68d86569c by Benjamin Peterson in branch '2.7': revert dd13098a5dc2 (#29006, #10513) https://hg.python.org/cpython/rev/74a68d86569c -- ___ Python tracker __

[issue10513] sqlite3.InterfaceError after commit

Changes by Benjamin Peterson : -- resolution: fixed -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue10513] sqlite3.InterfaceError after commit

Roundup Robot added the comment: New changeset dd13098a5dc2 by Benjamin Peterson in branch '2.7': revert 030e100f048a (#29006, #10513) https://hg.python.org/cpython/rev/dd13098a5dc2 -- ___ Python tracker __

[issue10513] sqlite3.InterfaceError after commit

Berker Peksag added the comment: This is now fixed in 2.7 and 3.5+. Thank you all for your patience! -- nosy: +berker.peksag resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6 -Python 3.4 ___ Python trac

[issue10513] sqlite3.InterfaceError after commit

Roundup Robot added the comment: New changeset 030e100f048a by Berker Peksag in branch '2.7': Issue #10513: Fix a regression in Connection.commit() https://hg.python.org/cpython/rev/030e100f048a -- ___ Python tracker

[issue10513] sqlite3.InterfaceError after commit

Roundup Robot added the comment: New changeset 81f614dd8136 by Berker Peksag in branch '3.5': Issue #10513: Fix a regression in Connection.commit() https://hg.python.org/cpython/rev/81f614dd8136 New changeset 685f32972c11 by Berker Peksag in branch 'default': Issue #10513: Merge from 3.5 https:/

[issue10513] sqlite3.InterfaceError after commit

Gian-Carlo Pascutto added the comment: I believe http://bugs.python.org/issue23129 is a dupe of this. The patch here has been in "patch review" for 9 months. That seems fairly long for something that's a regression that potentially silently produces the wrong data. -- nosy: +Gian-Carl

[issue10513] sqlite3.InterfaceError after commit

Changes by Claudiu Popa : -- stage: needs patch -> patch review versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___ _

[issue10513] sqlite3.InterfaceError after commit

Paul Melis added the comment: Just a bit more info on the patch. When running stock Python 2.7.4 the attached test script bug-binding_parameter_0.py returns: module: 2.6.0 sqlite: 3.7.9 Archives Archives/2011 Archives/2012 Traceback (most recent call last): File "bug-binding_parameter_0.py",

[issue10513] sqlite3.InterfaceError after commit

Changes by Ned Deily : -- nosy: -ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue10513] sqlite3.InterfaceError after commit

Paul Melis added the comment: Here's a patch that removes the pysqlite_do_all_statements(self, ACTION_RESET, 0); call. It also adds the sqlite error code to one of the exceptions raised, as the error message is misleading in case the ACTION_RESET is left in (I forgot what sqlite error is actua

[issue10513] sqlite3.InterfaceError after commit

Anders Blomdell added the comment: > So my suggestion is to remove in "pysql_connection_commit" the call to : > pysqlite_do_all_statements(self, ACTION_RESET, 0); > to bring back the correct old behavior. That's what I have been running for years, now... > And also eventually to remove in "pysq

[issue10513] sqlite3.InterfaceError after commit

Florent Viard added the comment: Hi, I encountered the same regression with python 2.7. I added a new testcase (testcase2) with another effect of the same problem. It is a model of what does python-storm when I try to do: for item in TableA.findall(): TableB.new_item(name=item.name) conne

[issue10513] sqlite3.InterfaceError after commit

Anders Blomdell added the comment: The culprit seems to be 'pysqlite_do_all_statements(self, ACTION_RESET, 0)' in pysqlite_connection_commit, which resets all active statements, but subsequent fetch/fetchall seems to trash the sqlite3 state in the statements. Removing the ACTION_RESET seems t

[issue10513] sqlite3.InterfaceError after commit

Ned Deily added the comment: Also fails with 3.2 as in 2.7 and works in 3.1 as in 2.6. -- nosy: +ghaering, ned.deily stage: -> needs patch type: crash -> behavior versions: +Python 3.2 ___ Python tracker

[issue10513] sqlite3.InterfaceError after commit

New submission from Anders Blomdell : With version 2.7 (and 2.7.1rc1), the following sequence (see attached test): c = cursor.execute(' select k from t where k == ?;', (1,)) conn.commit() r = c.fetchone() Traceback (most recent call last): File "/bugs/sqlite_bug.py", line 22, in