Re: Saving Image in Database [again] - Daniel da Veiga - com.mysql.lists.win32

1 message in com.mysql.lists.win32Re: Saving Image in Database [again]

From	Sent On	Attachments
Daniel da Veiga	30 Jul 2006 18:49

Subject:	Re: Saving Image in Database [again]
From:	Daniel da Veiga (dani...@gmail.com)
Date:	07/30/2006 06:49:34 PM
List:	com.mysql.lists.win32

On 7/30/06, Jay Blanchard <jbla...@pocket.com> wrote:

[snip] Was wondering if I could get a conversation started on the pros/cons of database storage verse filesystem [/snip]

There is additional overhead in saving and retrieving images from a database typically. Most folks benchmark to see which is faster and more efficient on their systems. YMMV.

BTW, this is a holy war of immense proportions and has been fought on many a list. If you will search MySQL lists archives, PHP list archives, JAVA archives, etc. you will see many an argument for/against/indifferent.

Exactly. The OP may forgive me, but there's really no point in start ANOTHER discussion about that, that are thousands of tests and benchmarks all over the web for image storage approuch, and the pros/cons of each system. Its all a matter of HOW you'll deal with the images, if they change a lot, if they are accessed a lot, if they're small, big, if your server is slow/fast, anyway, there are (like most benchmarks) a high number of variables that affect in a way or another the performance and what you get from each approuch.

There was a discussion about it high here at MySQL win32 a few weeks ago, I PERSONALLY have found filesystem storage to be better FOR MY PARTICULAR systems. But that does not apply to every application, and could be easily put down for a database storage in the case of, for example, distributed and integrated editing and retrieval.

So, my advice, analyse WHAT you need, project what you WILL need, and search the web. That would be the best result you can get.