BSDDB set_location bug

[mcfletch]

BPO	890872
Nosy	@gpshead
Files	bsddb_error_demo.py: Test for bsddb set_location error for btree databases

^{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 = 'https://github.com/gpshead'
closed_at = <Date 2004-07-13.21:14:16.000>
created_at = <Date 2004-02-05.09:08:52.000>
labels = ['library']
title = 'BSDDB set_location bug'
updated_at = <Date 2004-07-13.21:14:16.000>
user = 'https://bugs.python.org/mcfletch'

bugs.python.org fields:

activity = <Date 2004-07-13.21:14:16.000>
actor = 'gregory.p.smith'
assignee = 'gregory.p.smith'
closed = True
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2004-02-05.09:08:52.000>
creator = 'mcfletch'
dependencies = []
files = ['1197']
hgrepos = []
issue_num = 890872
keywords = []
message_count = 3.0
messages = ['19916', '19917', '19918']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'mcfletch', 'chomo']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue890872'
versions = ['Python 2.3']

[mcfletch]

In module \lib\bsddb\init.py line 147, the method
set_location() uses self.dbc.set(key) , which raises an
error if the key is not found. It should be using
self.dbc.set_range(key) , which matches the documented
behaviour for btree databases.

Test for correct behaviour is attached.

Behaviour is seen under Python 2.3.3 win32 binary build.

[chomo]

Logged In: YES
user_id=943591

looks like need testcase

[gpshead]

Logged In: YES
user_id=413

this has been fixed in both HEAD and python 2.3 cvs with a
test case. (appears to have been committed a while ago)