Skip Menu |

This queue is for tickets about the BerkeleyDB CPAN distribution.

Report information
The Basics
Id: 19821
Status: resolved
Priority: 0/
Queue: BerkeleyDB

People
Owner: pmqs [...] cpan.org
Requestors: DONGXU [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.27
Fixed in: (no value)



Subject: db_put with DB_APPEND returns wrong recno
Hello, I found that db_put with DB_APPEND will return the recno 0 by inserting k/v into the newly created Recno database. This bug is assumed to be fixed in Berkeley ver 4.0.14 My version is 4.2 I created a primary Recno database with secondary Hash index, a db_pget or c_pget against the secondary Hash database will always returns a primary key which is the actual record number plus 1. --- BR / Dongxu
On Sat Jun 10 23:42:18 2006, DONGXU wrote: Show quoted text
> Hello, > > I found that db_put with DB_APPEND will return the recno 0 by inserting > k/v into the newly created Recno database. > This bug is assumed to be fixed in Berkeley ver 4.0.14 > My version is 4.2 > > I created a primary Recno database with secondary Hash index, a db_pget > or c_pget against the secondary Hash database will always returns a > primary key which is the actual record number plus 1.
I'm not clear if this is the same problem as your #19820 problem report. If it is still an issue with the new version (0.28) that is now on CPAN, can you provide me with more information about the error - some code to allow me to reproduce what you are seeing would be best. cheers Paul
Subject: Re: [rt.cpan.org #19821] db_put with DB_APPEND returns wrong recno
Date: Mon, 12 Jun 2006 14:06:21 +0800
To: bug-BerkeleyDB [...] rt.cpan.org
From: "Dongxu Ma" <dongxu.ma [...] gmail.com>
On 6/12/06, Paul Marquess via RT <bug-BerkeleyDB@rt.cpan.org> wrote: Show quoted text
> > > <URL: http://rt.cpan.org/Ticket/Display.html?id=19821 > > > On Sat Jun 10 23:42:18 2006, DONGXU wrote:
> > Hello, > > > > I found that db_put with DB_APPEND will return the recno 0 by inserting > > k/v into the newly created Recno database. > > This bug is assumed to be fixed in Berkeley ver 4.0.14 > > My version is 4.2 > > > > I created a primary Recno database with secondary Hash index, a db_pget > > or c_pget against the secondary Hash database will always returns a > > primary key which is the actual record number plus 1.
> > I'm not clear if this is the same problem as your #19820 problem report. > If it is still an issue with the new version (0.28) that is now on CPAN, > can you provide me with more information about the error - some code to > allow me to reproduce what you are seeing would be best.
confused by BerkeleyDB Docus on sleepycat. It is said that recno should start with 1 while I dumped the real db, at least it starts from 0 on my machine; P This should _NOT_ be a bug of the binding. Sorry, please close __TICKET__. cheers Show quoted text
> Paul > > >
-- Cheers, Dongxu __END__ dongxu.wordpress.com search.cpan.org/~dongxu