Nathan Kidd wrote:
> Les Mikesell wrote:
>> Nathan Kidd wrote:
>>> I think that's a little unfair to BDB. Yes there are many reports of
>>> "my BDB repo has 'crashed'", but invariably it is a result of new
>>> users not understanding BDB's behaviour when an operation is
>>> improperly interrupted ("wedging"). This has nothing to do with
>>> "caring about your data" but ease of use with the server (i.e. data
>>> is not lost, you just need to manually run 'svnadmin recover'). An
>>> more experienced admin can set things up so this never becomes a
>>> problem. New BDB's auto-recover from "wedging" so it isn't an issue
>>> at all any more.
>>
>> I think a lot of people have had bad experiences with BDB in other
>> contexts in the past, so it's going to take a while to trust that it
>> is any better this time around.
>
> Can you recall specific cases?
In my case it was a web forum program written before such things were
commonplace by someone who preceded me. It stored the login names and
passwords in a bdb along with the list of topics and last-read messages.
After the original authors left (of course...) the topic list grew to
a point where the space originally allocated for the value was not
enough and it should have been relocated as they accumulated in a users
list. But, back then there must have been an off-by-one error in this
decision because it would randomly overwrite some nearby users who would
then not be able to log in.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 9 19:59:04 2007