glad to hear there's a happy medium between flat files and a full server based db. the main reason why i wanted to avoid server based db is that all my motorcycle friends use windows, and i was hoping to write something that they could use too.
sounds like when i get need a break from my research, i should read perl DBI book. honestly, i barely even know what a database is beyond the obvious and certainly don't know any sql. this is a topic that i've been wanting to learn for awhile (but all the books i've seen on the topic are really long boring... :( ). pete begin Henry House <[EMAIL PROTECTED]> > On Tue, Mar 12, 2002 at 10:50:10PM -0800, Bill Broadley wrote: > > I won't go into details, but in summary I'd strongly recommend > > a SQL database for anything much more complicated then a small table > > or two. I'll list some of the things you should consider if your > > going to do it yourself: > > I don't disagree with the wise words from you and Ted about the folly of > rolling one's own data storage system, but Peter's original point, if I recall > correctly, was that he did not want a server-based database (on account of > the administration burden, presumably). > > The choice is not just between flat files and a full-blow RDBMS. There are > tools midway in between. Berkely DB version 3 has bindings available for more > languages that you can shake a stick at, and has efficient binary storage and > proper locking for multi-user access. SQLite implements a multi-user database > manipulated in SQL in a library (no server). > > On the other hand, I can wholeheartedly recommend PostgreSQL, even though is > is a rather heavyweight server. Pick your worse evil ;-). > > -- > Henry House > The attached file is a digital signature. See <http://romana.hajhouse.org/pgp> > for information. My OpenPGP key: <http://romana.hajhouse.org/hajhouse.asc>. _______________________________________________ vox-tech mailing list [EMAIL PROTECTED] http://lists.lugod.org/mailman/listinfo/vox-tech
