Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 45886 invoked from network); 20 Mar 2003 13:17:15 -0000 Received: from zebra.zinkwazi.com (66.139.79.200) by daedalus.apache.org with SMTP; 20 Mar 2003 13:17:15 -0000 Received: (from dallen@localhost) by zebra.zinkwazi.com (8.11.6/8.11.6) id h2KDHFf31515 for torque-user@db.apache.org; Thu, 20 Mar 2003 07:17:15 -0600 Date: Thu, 20 Mar 2003 07:17:15 -0600 From: Dan Allen To: Turbine Torque Users List Subject: Re: How to read/write images to/from db Message-ID: <20030320071715.A18095@mojavelinux.com> References: <002301c2ee19$07a4a920$bec6e6d9@yomama> <009801c2ee23$a4a359b0$6601a8c0@complexity> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <009801c2ee23$a4a359b0$6601a8c0@complexity>; from bschneider@vecna.com on Wed, Mar 19, 2003 at 09:27:17AM -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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, 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -