Issue 20562: sqlite3 returns result set with doubled first entry

Created on 2014-02-08 12:43 by jwezel, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (4)
msg210622 - (view)	Author: Johnny Wezel (jwezel)	Date: 2014-02-08 12:43
I could isolate a bug where sqlite3 returns a result set from a select where the first entry occurs twice. >>> sys.version_info sys.version_info(major=2, minor=7, micro=5, releaselevel='final', serial=0) >>> import sqlite3 >>> sqlite3.version_info (2, 6, 0) $ uname -a Linux 3.10.25-gentoo #1 SMP PREEMPT Wed Jan 29 18:05:47 CET 2014 x86_64 Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux
msg210655 - (view)	Author: R. David Murray (r.david.murray) *	Date: 2014-02-08 14:52
Here is an even more cut down example. Note that removing the commit avoids the problem.
msg221680 - (view)	Author: PCManticore (Claudiu.Popa) *	Date: 2014-06-27 07:09
issue10513 has a patch that fixes this problem as well.
msg273724 - (view)	Author: Berker Peksag (berker.peksag) *	Date: 2016-08-26 20:22
This is basically a duplicate of issue 10513.

History
Date	User	Action	Args
2022-04-11 14:57:58	admin	set	github: 64761
2016-08-26 20:22:05	berker.peksag	set	status: open -> closed superseder: sqlite3.InterfaceError after commit nosy: + berker.peksag messages: + msg273724 resolution: duplicate stage: resolved
2015-01-11 01:59:45	ghaering	set	assignee: ghaering nosy: + ghaering
2014-06-27 07:39:30	rhettinger	set	priority: normal -> high
2014-06-27 07:09:05	Claudiu.Popa	set	nosy: + Claudiu.Popa messages: + msg221680
2014-02-08 14:52:30	r.david.murray	set	files: + t.py versions: + Python 3.3, Python 3.4 nosy: + r.david.murray messages: + msg210655
2014-02-08 12:43:08	jwezel	create