in reply to Re: Mysql & perl
in thread Mysql & perl

To be fair, one problem I have with not storing the data in a database is the issue of maintainability. Imagine if you only have one script, one database, and one path for the images. That's three pieces to the puzzle instead of two. The more you toss in, the more difficult the system is to maintain when you come back to it later. If you are creating a document management system, you'd probably have many scripts and tables. Adding many paths to store documents in is just adding to the complexity (IMHO).

Cheers,
Ovid

Replies are listed 'Best First'.
RE: RE: Re: Mysql & perl
by Aighearach (Initiate) on Jul 15, 2000 at 07:15 UTC
    OTOH, putting the images into the database means that if you have to move the stuff around, there is a lot less to move. Also, if you are going to put the data on a different network node than the script, having everything in the database reduces the logical complexity.
    Paris Sinclair    |    4a75737420416e6f74686572
    pariss@efn.org    |    205065726c204861636b6572
    I wear my Geek Code on my finger.