Javier Omella wrote:
John dijo:
Everything must be done via perl.
I have already download vsftp for trasferring the files (Net::FTP) BUt is it a good idea to store gifs (~100 Kb) in a Mysql database or to store the images in the file system directly?
I don´t think it is a good idea, some guys maybe think is ok but in my personal experience is more slow and you have much development, and in
Well, storing the to file system it sounds much better. But how could a
backup be done?
I mean automating the backup process via a script.
Tarring, gzipping all the directories containing the images and copy them to
where?
----- Original Message -----
From: "Tom Allison"
future if for some reason you are adding more weight images, your system will be even more slow. Maybe in DB like Oracle or M$SQL with store procedures!! Security? yes, it is more secure in the DB, but, it´s just question of doing things right
Maybe someone here have a different experience than me, and can share it.
cheers.
Sorry, my english sucks :)
Even in Oracle this is a really bad idea. I know because I had this conversation with someone who is an Oracle DBA last week about it.
You store the links to the images (/var/spool/pictures/winter/p001.jpg) before you store the body in the database.
This way you can do a few things with the database. Back up is easier because you don't have to manage a binary block of data that never changes. You can visually verify that the images called are the images seen. You can do debugging more easily by keeping the images in a space that is readily accessable for you to look at.
Putting it into a database gaurantees that you will never be able to debug it without building a bunch of software to pull the image out of the database for you, but that software has to be 100% bug free...
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com