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 9A436D1B345
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Fri,  2 Jul 2004 14:50:11 -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 80476-10
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Fri,  2 Jul 2004 17:50:11 +0000 (GMT)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.207])
	by svr1.postgresql.org (Postfix) with SMTP id 2BF00D1B373
	for <pgsql-hackers@postgresql.org>;
	Fri,  2 Jul 2004 14:50:08 -0300 (ADT)
Received: by mproxy.gmail.com with SMTP id 73so68955rne
	for <pgsql-hackers@postgresql.org>;
	Fri, 02 Jul 2004 10:50:09 -0700 (PDT)
Received: by 10.38.79.11 with SMTP id c11mr24258rnb;
	Fri, 02 Jul 2004 10:50:08 -0700 (PDT)
Message-ID: <f96a9b8304070210502c42da29@mail.gmail.com>
Date: Fri, 2 Jul 2004 19:50:08 +0200
From: Jochem van Dieten <jochemd@gmail.com>
To: Hannu Krosing <hannu@tm.ee>
Subject: Re: Adding column comment to information_schema.columns
Cc: PostgreSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
In-Reply-To: <1088769438.15415.1.camel@fuji.krosing.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <40E37E3F.2050400@telstra.net> <22066.1088656403@sss.pgh.pa.us>
	<40E3949F.6020201@telstra.net> <40E3BB25.4020804@pse-consulting.de>
	<k6xn3cph.fsf@bullysports.com> <40E4C305.4070309@familyhealth.com.au>
	<40E4C367.2080303@telstra.net>
	<1088769438.15415.1.camel@fuji.krosing.net>
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/123
X-Sequence-Number: 55684

On Fri, 02 Jul 2004 14:57:18 +0300, Hannu Krosing <hannu@tm.ee> wrote:
> 
> 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_'

I didn't write that (or at least, I didn't mean to write that :-). The
SQL standard tells that they will not use trailing underscores,
therefore *my* conclusion is that it is future proof (from a standards
perspective) if all PostgreSQL extensions use a trailing underscore.
Which also gives an indication to the user that it is a PostgreSQL
extension.

"NOTE 77 - It is the intention that no <key word> specified in ISO/IEC
9075 or revisions thereto shall end with an <underscore>."
ISO/IEC 9075-2:2003   5.4   Names and Identifiers

Jochem