LPM: RE: dbms

[ken.rietz at asbury.edu]

> i'm working on a project that involves perl meshing with a database
> (flatfile, four/five fields). we're using postgresql right 
> now as that was
> what was here when we started. i'm trying to escape the grasp 
> of postgres
> because this project really doesnt call for it. the problem 
> is this: i've
> tried dbm and mldbm but they are very machine specific. two 
> machines with
> the same versions of perl and the necessary modules could not 
> read each
> others dbms.  any thoughts on alternative solid perl db/dbm systems?


1. I can understand wanting to get out of postgresql, but what do
you mean by "this project really doesn't call for it"? Do you want
less than a flatfile, four/five fields database? How about just writing
a file with hashes and reading back from it?

2. If you want more machine and database independence, look carefully
at the DBI module, with appropriately-used DBD's to handle the dependent
parts. (I thought you were already doing that, so this puzzles me.) You
should be able to read out of one database and write straight to another.
My suggestion (I'm sure seconded by Rich) would be MySQL for just about
any DB work you need.

-- Ken