This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: fix bsddb test associate problems w/bsddb 4.1
Type: Stage:
Components: Extension Modules Versions:
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: gregory.p.smith Nosy List: gregory.p.smith, hfoffani, nnorwitz
Priority: normal Keywords: patch

Created on 2006-01-17 07:51 by nnorwitz, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
bsddb-assoc.patch nnorwitz, 2006-01-17 07:51 v1
Messages (4)
msg49330 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2006-01-17 07:51
I think that's what this patch fixes.  Just wanted to
get up here and find a BSD DB knowledgable person to
comment.
msg49331 - (view) Author: Hernan Foffani (hfoffani) Date: 2006-01-24 15:08
Logged In: YES 
user_id=112690

I would recommend to upgrade to 4.2 or newer instead.  See:
http://subversion.tigris.org/faq.html#bdb41-tabletype-bug

msg49332 - (view) Author: Hernan Foffani (hfoffani) Date: 2006-01-24 15:22
Logged In: YES 
user_id=112690

Sorry, "instead" is not the right word here.  I meant that I
wouldn't give too much support to bsddb 4.1.  Users of it
ought to know the problem that it carries.  I haven't seen
at the original problem though.
msg49333 - (view) Author: Gregory P. Smith (gregory.p.smith) * (Python committer) Date: 2006-01-24 19:57
Logged In: YES 
user_id=413

thanks!  this appears to work.  I tested it with BerkeleyDB
3.2 thru 4.4.  4.2-4.4 already worked fine; this patch fixes
associate in 3.3 thru 4.1.  (3.2 does not support associate)

commit id 42173.

Supporting older BerkeleyDB versions can be annoying but
when its easy lets do it.  I agree with hfoffani that
serious bsddb users should consider >= 4.2.
History
Date User Action Args
2022-04-11 14:56:15adminsetgithub: 42802
2006-01-17 07:51:54nnorwitzcreate