Gian-Carlo Pascutto added the comment:
>Then we wait for someone that really knows why the change was done in the
>first place.
Python 2.7 had a regression compared to 2.6 where a SELECT after a COMMIT would
silently return the wrong data:
http://bugs.python.org/issue2312
Gian-Carlo Pascutto added the comment:
I've ran into this as well, when a program that was running correctly with
PostgreSQL turned out to produce garbage with SQLite. Code to reproduce roughly
looks like this:
sel_cursor = conn.cursor()
sel_cursor.execute(SELECT prim_key_id FROM
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-Carlo
