in reply to database problems

You didn't mention that you _HAVE_ to use DB_File's, so . . .

Sounds like you need a relational database. DB_File's are fine and dandy, but as soon as you start adding 'users', you really should 'upgrade'.

As well as being able to handle multiple users reading and writing the data at any time, you also get the added benefit of normalized data. You can join tables together and use SQL to selectively retrieve and sort the data.

I recommend looking into MySQL and Postgres.

If you aren't convinced, then please read the words of my friend eduardo: Re: DBI vs MLDBM/GDBM_File.

Jeff

R-R-R--R-R-R--R-R-R--R-R-R--R-R-R--
L-L--L-L--L-L--L-L--L-L--L-L--L-L--

Replies are listed 'Best First'.
Re: (jeffa) Re: database problems
by dl748 (Initiate) on Jun 02, 2001 at 03:07 UTC
    i understand your reasoning. But aren't MySQL and Postgres "servers" that must be installed on my server. All I need to store is a Key=>Pair. I don't need complex database engines. All I was hoping for is one that lock and unlocks but does not cache. Maybe an example. And No I didn't say say I had to use DB_File. I know Unix and Linux have hundreds of files that multiple users read and write from and They don't have this problem nor have to install some server system to do their work for them. I'm thinking there are functions that I can use also.