Repository navigation
sqlite3 returns result set with doubled first entry #64761
Description
| BPO | 20562 |
|---|---|
| Nosy | @bitdancer, @PCManticore, @berkerpeksag |
| Superseder | |
| Files |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2016-08-26.20:22:05.574>
created_at = <Date 2014-02-08.12:43:08.285>
labels = ['extension-modules', 'type-bug']
title = 'sqlite3 returns result set with doubled first entry'
updated_at = <Date 2016-08-26.20:22:05.572>
user = 'https://bugs.python.org/jwezel'bugs.python.org fields:
activity = <Date 2016-08-26.20:22:05.572>
actor = 'berker.peksag'
assignee = 'ghaering'
closed = True
closed_date = <Date 2016-08-26.20:22:05.574>
closer = 'berker.peksag'
components = ['Extension Modules']
creation = <Date 2014-02-08.12:43:08.285>
creator = 'jwezel'
dependencies = []
files = ['33992', '33998']
hgrepos = []
issue_num = 20562
keywords = []
message_count = 4.0
messages = ['210622', '210655', '221680', '273724']
nosy_count = 5.0
nosy_names = ['ghaering', 'r.david.murray', 'Claudiu.Popa', 'berker.peksag', 'jwezel']
pr_nums = []
priority = 'high'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = '10513'
type = 'behavior'
url = 'https://bugs.python.org/issue20562'
versions = ['Python 2.7', 'Python 3.3', 'Python 3.4']
Activity
jwezel commentedon Feb 8, 2014
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/Linuxbitdancer commentedon Feb 8, 2014
Here is an even more cut down example. Note that removing the commit avoids the problem.
PCManticore commentedon Jun 27, 2014
bpo-10513 has a patch that fixes this problem as well.
berkerpeksag commentedon Aug 26, 2016
This is basically a duplicate of bpo-10513.