I had a similar problem and was advised that the native filesystem is faster
than doing lookups and some sort of rendering. So storing the link in the
db will do it, and then just have the images at the pointed-to location.
----- Original Message -----
From: "ESV Media GmbH" <mysql_list@stripped>
Sent: Thursday, November 17, 2005 1:18 AM
Subject: Image Storage -- Better to store them on the Filesystem or in the
> we´ve large amount of Images ( nearly 2 GB ).
> And they will increase, cause or Editors will submit several articles a
> day where they´re allowed to upload
> some new pics.
> So, whats the better solution ? To store them in the filesystem ( with
> only the path in the db )
> or to store them as BLOB´s in the DB.
> When we decide to store them in the DB, we´ve thought about splitting
> larger Images ( > 64 K ) into several pieces into the db.
> So, we´ve a simulated "streaming". I´ve seen it at
> So, any recommendation is very welcome.I would really appreciate any of
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1