X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4CB1ED1EB0A for ; Thu, 6 May 2004 09:55:26 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 46941-07 for ; Thu, 6 May 2004 09:55:07 -0300 (ADT) Received: from fep01-mail.bloor.is.net.cable.rogers.com (fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71]) by svr1.postgresql.org (Postfix) with ESMTP id 84101D1EAA6 for ; Thu, 6 May 2004 09:55:03 -0300 (ADT) Received: from phlogiston.dydns.org ([65.49.125.184]) by fep01-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20040506125319.YGDM79524.fep01-mail.bloor.is.net.cable.rogers.com@phlogiston.dydns.org> for ; Thu, 6 May 2004 08:53:19 -0400 Received: by phlogiston.dydns.org (Postfix, from userid 1000) id 576AB3C8D; Thu, 6 May 2004 08:55:06 -0400 (EDT) Date: Thu, 6 May 2004 08:55:06 -0400 From: Andrew Sullivan To: pgsql-sql@postgresql.org Subject: Re: not really SQL but I need info on BLOBs Message-ID: <20040506125506.GA14119@phlogiston.dyndns.org> Mail-Followup-To: pgsql-sql@postgresql.org References: <004401c4332a$cee69f00$0b00a8c0@forge> <20040506114622.26803.qmail@web41007.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040506114622.26803.qmail@web41007.mail.yahoo.com> User-Agent: Mutt/1.5.5.1+cvs20040105i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep01-mail.bloor.is.net.cable.rogers.com from [65.49.125.184] using ID at Thu, 6 May 2004 08:53:19 -0400 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/58 X-Sequence-Number: 17772 On Thu, May 06, 2004 at 04:46:22AM -0700, Theodore Petrosky wrote: > Thanks for the reply. Are there (in your opinion) > reasons why you would choose to store the images in > the db? Transactional integrity. If there's a risk that people are going to be deleting, &c. these images, then you can end up with references in the database to files that don't exist, because the filesystem operations can't be made subject to the transactions of the database. A -- Andrew Sullivan | ajs@crankycanuck.ca