From: Justin Clift <jc@telstra.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Subject: Re: Adding column comment to information_schema.columns
Date: Thu, 01 Jul 2004 14:35:43 +1000
Message-ID: <40E3949F.6020201@telstra.net> (raw)
In-Reply-To: <22066.1088656403@sss.pgh.pa.us>
References: <40E37E3F.2050400@telstra.net>
<22066.1088656403@sss.pgh.pa.us>
Tom Lane wrote:
> Justin Clift <jc@telstra.net> writes:
>
>>Not sure how worthwhile others will find this small patch (to CVS HEAD),
>>but we found it useful. It adds the column comments to the
>>information_schema.columns view.
>
>
> This question has been touched on before, but I guess it's time to face
> it fair and square: is it reasonable for an SQL implementation to add
> implementation-specific columns to an information_schema view? One
> could certainly argue that the entire point of information_schema is
> to be *standard*, not more, not less. OTOH I do not know if adding
> an extra column is likely to break anyone's application. Comments?
Well, I suppose it reduces application portability if anyone starts
relying on it.
?
Regards and best wishes,
Justin Clift
> regards, tom lane
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: jc@telstra.net, tgl@sss.pgh.pa.us
Subject: Re: Adding column comment to information_schema.columns
In-Reply-To: <40E3949F.6020201@telstra.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox