X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1B115D1B174 for ; Fri, 2 Jul 2004 11:12:17 -0300 (ADT) 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 59056-10 for ; Fri, 2 Jul 2004 14:12:19 +0000 (GMT) Received: from bramble.mmrd.com (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id 68598D1B43C for ; Fri, 2 Jul 2004 11:12:14 -0300 (ADT) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id i62Cip9U013062; Fri, 2 Jul 2004 08:44:54 -0400 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [10.225.10.110]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id i62EC8N18782; Fri, 2 Jul 2004 10:12:08 -0400 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id NS17YWCS; Fri, 2 Jul 2004 10:12:06 -0400 Subject: Re: Adding column comment to information_schema.columns From: Robert Treat To: Hannu Krosing Cc: Justin Clift , PostgreSQL Hackers Mailing List In-Reply-To: <1088769438.15415.1.camel@fuji.krosing.net> References: <40E37E3F.2050400@telstra.net> <22066.1088656403@sss.pgh.pa.us> <40E3949F.6020201@telstra.net> <40E3BB25.4020804@pse-consulting.de> <40E4C305.4070309@familyhealth.com.au> <40E4C367.2080303@telstra.net> <1088769438.15415.1.camel@fuji.krosing.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 02 Jul 2004 10:12:07 -0400 Message-Id: <1088777527.31171.342.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/100 X-Sequence-Number: 55661 On Fri, 2004-07-02 at 07:57, Hannu Krosing wrote: > On R, 2004-07-02 at 05:07, Justin Clift wrote: > > Christopher Kings-Lynne wrote: > > >> There is a huge difference between adhering to a standard and limiting > > >> yourself to a standard. The real question is whether PostgreSQL's > > >> goal is to support SQL standards, or whether PostgreSQL's goal is to > > >> give PostgreSQL users a useful set of tools. > > > > > > > > > There are literally _hundreds_ of fields we could add to the > > > information_schema. Either we add them all or we add none of them. > > > > Well, if we add them (and they would be very useful I reckon) should we > > ensure there's an obvious PG naming thing happening? > > > > i.e. pg_column_comment > > > > or similar? Maybe not "pg_" but you know what I mean. > > IIRC we were recently told (in this thread) that the SQL standard tells > to end local customisations with underscore, so it would be > 'column_comment_' > Yup... but before we go to far I think anyone who is thinking of adding a column should see if there is a comparable column in oracle/db2/$ql$erver. The point of information_schema (at least one point of it) is to help application writers to write code that works across different database systems and I wouldn't be surprised if those folks had already extended the information_schema in some way. Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL