Author anders.blomdell@control.lth.se
Recipients anders.blomdell@control.lth.se, ghaering, ned.deily
Date 2010-11-24.10:08:11
SpamBayes Score 7.60527e-09
Marked as misclassified No
Message-id <1290593297.3.0.671039363955.issue10513@psf.upfronthosting.co.za>
In-reply-to
Content
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 to bring back old behaviour (if it's the correct fix is, however, beyond me).

Slightly modified testprogram that shows more wierdness; output from:

    c =  cursor.execute(' select k from t where k == ?;', (0,))
    conn.commit()
    print c.fetchall()

is:

    [(0,), (0,)]

which is not what I would expect with a primary key...
History
Date User Action Args
2010-11-24 10:08:17anders.blomdell@control.lth.sesetrecipients: + anders.blomdell@control.lth.se, ghaering, ned.deily
2010-11-24 10:08:17anders.blomdell@control.lth.sesetmessageid: <1290593297.3.0.671039363955.issue10513@psf.upfronthosting.co.za>
2010-11-24 10:08:11anders.blomdell@control.lth.selinkissue10513 messages
2010-11-24 10:08:11anders.blomdell@control.lth.secreate