in reply to Re: DBI vs MLDBM/GDBM_File
in thread DBI vs MLDBM/GDBM_File, etc.

I have seen Text::CSV_XS, and I also know of the existence of DBD::CSV. But the problem is that a CSV file is still a flat text file, with no direct indexing capabilities. And that's precisely what I want: to avoid having to rewrite the whole file every time I make a change.

I'd like to avoid MySQL because you need to have the server running. I would like to have something standalone.

Thanks,

--ZZamboni

Replies are listed 'Best First'.
RE: RE: Re: DBI vs MLDBM/GDBM_File
by KM (Priest) on Jul 03, 2000 at 23:32 UTC
    If you want something standalone, try DBD::RAM. You can still have the SQL syntax and whatnot without the server. However, you then do not get the benefits of a server, such as threading, indexing, locking (heaven forbid someone changes your flat files), control over who accesses your data, etc... Out of curiosity, why do you want it standalone? Because you don't want to muck with a server, or a design reason of some sort?

    Cheers,
    KM

[reply]
      It's partly because I don't want to muck with a server, but mostly because it's a system administration tool, and I don't want people to need a running DB server to use it. In this sense it's a design decision, I guess.

      --ZZamboni

[reply]
        Ah, gotcha. There would only really be one DB server needed, you would just need the DB client running on the machines which need access. So, DBD::RAM or the like would be good to look into.

        Cheers,
        KM

[reply]

In Section Seekers of Perl Wisdom