X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DBC3DD9F77 for ; Sun, 27 Nov 2005 16:33:31 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23642-01 for ; Sun, 27 Nov 2005 16:33:31 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from stark.xeocode.com (stark.xeocode.com [216.58.44.227]) by svr1.postgresql.org (Postfix) with ESMTP id 72434D7EF9 for ; Sun, 27 Nov 2005 16:33:29 -0400 (AST) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1EgTD8-0003xR-00; Sun, 27 Nov 2005 15:33:22 -0500 To: Rob Cc: pgsql-sql@postgresql.org Subject: Re: Storing HTML in table References: In-Reply-To: From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 27 Nov 2005 15:33:22 -0500 Message-ID: <87zmnpj0fh.fsf@stark.xeocode.com> Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/259 X-Sequence-Number: 23510 Rob writes: > I would like complete control over this information -- so if sometime in the > future it's decided to totally redesign the layout. Also, at some point a > tool will be created so novice computer users can enter nicely formatted > markup -- meaning you won't have to know HTML to use this tool. You should go look at some of the XML database books out there and maybe you'll find a tool to do what you want. But beware, there's a lot of snake-oil in this field. Anyone who promises a one-size-fits-all solution to every problem is probably deluded. The problem is hard. There's an inherent tension between being able to easily manipulate parts of the data and flexibility in the type of data you can represent. One one side is the traditional relational database model where every record must contain precisely the same fixed list of predetermined columns. One the other side is the decidely non-relational model where you just store a large hunk of xml text. What you're looking for is one of the many systems that attempt to bridge these two extremes and provide the best of both worlds. -- greg