db-torque-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Eade <se...@backstagetech.com.au>
Subject Re: How to read/write images to/from db
Date Thu, 20 Mar 2003 22:37:06 GMT
One problem with storing the images as files is that it becomes harder to
dynamically manage the security of the images if the ability to view them
needs to be controlled on a per user basis.

Most applications won't need to worry about this though.

Scott
-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
.Mac Chat/AIM: seade at mac dot com


On 21/03/2003 12:17 AM, "Dan Allen" <dan@mojavelinux.com> wrote:

> It is pretty much a consensus that storing images in a database is
> an unnecessary overhead, not because the database can't handle BLOBs
> (although the relational aspect of searching and filtering is pretty
> much lost with BLOB fields) but that a browser must issue a new
> request each time you want to dish out an image because there is no
> way for the browser to make a hard cache link.  You should store
> only meta data and a file reference in the database, perhaps even
> only a relative file reference in case your data storage location
> changes.
> 
> Dan


Mime
View raw message