X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id ACE1AD1DD17 for ; Sun, 29 Feb 2004 14:08:12 +0000 (GMT) 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 94812-07 for ; Sun, 29 Feb 2004 10:08:14 -0400 (AST) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by svr1.postgresql.org (Postfix) with ESMTP id B8C13D1D85F for ; Sun, 29 Feb 2004 10:08:09 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-31.mail.demon.net with esmtp (Exim 3.35 #1) id 1AxRc4-000CJ2-0V; Sun, 29 Feb 2004 14:08:12 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 65A191741E; Sun, 29 Feb 2004 14:08:10 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id BE5D617228; Sun, 29 Feb 2004 14:08:07 +0000 (GMT) From: Richard Huxton To: Tom Lane Subject: Re: [ADMIN] Schema comparisons Date: Sun, 29 Feb 2004 14:08:07 +0000 User-Agent: KMail/1.5 Cc: Mark Lubratt , pgsql-hackers@postgresql.org References: <200402281759.50389.dev@archonet.com> <11549.1078020095@sss.pgh.pa.us> In-Reply-To: <11549.1078020095@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402291408.07797.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/983 X-Sequence-Number: 50572 On Sunday 29 February 2004 02:01, Tom Lane wrote: > Richard Huxton writes: > > I've been looking at storing $REVISION$ in comments for each object, so > > my install scripts can halt if there is a problem. Not wanting to use my > > only comment slot for this I was thinking about an extension to the > > COMMENT ON statement: > > COMMENT ON TABLE foo IS 'This is where I stroe my foos.'; > > COMMENT ON TABLE foo SECTION 'default' IS 'I meant store my foos.'; > > COMMENT ON TABLE foo SECTION 'revision' IS '1.19'; > > COMMENT ON TABLE foo SECTION 'bar' IS 'baz'; > > This seems a little, um, specialized. Why don't you just keep the info > in a user-defined table? For the same reasons you don't store existing comments in a user-defined table: 1. It's convenient to have a standard (across providers) place for them. 2. It's meta-data, not data. 3. It gets dumped along with my table. If it's just a case of "looks like a waste of time" then I might well waste my time and do it. On the other hand, if it's a case of "unnecessary complication - don't want it in the code" then I'll not bother. -- Richard Huxton Archonet Ltd