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 -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Daniel Allen, <[EMAIL PROTECTED]> http://www.mojavelinux.com/ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Real programmers just hate to get up in the morning, and contrary to Ordinary People, they're in better shape as it gets closer to nighttime. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
