Re: Re: Re: tied hashed and deleting keys and their valeus

Well, the speed vs. space trade off is the most common optimization there is. In this case it is a perfectly fine tradeoff that they made. How often do you think it is that DBs shrink significantly?

--
$you = new YOU;
honk() if $you->love(perl)

Comment on Re: Re: Re: tied hashed and deleting keys and their valeus

Replies are listed 'Best First'.
Re: Re: Re: Re: tied hashed and deleting keys and their valeus by skazat (Chaplain) on Feb 01, 2001 at 02:51 UTC
I use the DB File to save mailings from a lightweight Mailing List Manager I develop. The only time something needs to be removed is when the administrator deletes an email message that saved in the DB FIle archive. The keys are created using the date, so no 2 keys are ever used twice. If the removed entries' space is reused later, that's perfectly fine. My test archive was about 3.5 megs, about 100 messages worth. I still have the problem of entries not being removed at all. Anyone else have this? -justin simoni !skazat!	[reply]
Re: {5} tied hashed and deleting keys and their valeus by jeroenes (Priest) on Feb 01, 2001 at 18:37 UTC
Nobody seems to reply here, and I feel somebody should... but I think other monks could provide better insights. I don't know very much about the other dbases mentioned in AnyDBM_File. It appears that you have a choice. Which DBM are you using? Your 'lack of deletion' may be a DBM related problem. Have you tried the same test using BerkeleyDB? If it's not on your system, point your browser to sleepycat. If you want further discussion, just /msg me. Cheers, Jeroen "We are not alone"(FZ)	[reply]