| From: | Justin Clift <jc(at)telstra(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding column comment to information_schema.columns |
| Date: | 2004-07-01 04:35:43 |
| Message-ID: | 40E3949F.6020201@telstra.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Justin Clift <jc(at)telstra(dot)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
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | joseph speigle | 2004-07-01 05:02:22 | possibly updating techdocs; mysql2pgsql on gborg |
| Previous Message | Tom Lane | 2004-07-01 04:33:23 | Re: Adding column comment to information_schema.columns |