| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Justin Clift <jc(at)telstra(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding column comment to information_schema.columns |
| Date: | 2004-07-01 07:20:05 |
| Message-ID: | 40E3BB25.4020804@pse-consulting.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Clift wrote:
> Tom Lane wrote:
>
>>
>> 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.
We're advertising to do pure ANSI, so we'd mislead people if we supplied
non-standard columns.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2004-07-01 07:30:28 | Re: Adding column comment to information_schema.columns |
| Previous Message | Christopher Kings-Lynne | 2004-07-01 07:11:27 | Re: Adding column comment to information_schema.columns |