Re: Adding column comment to information_schema.columns

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Clift <jc(at)telstra(dot)net>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adding column comment to information_schema.columns
Date: 2004-07-01 07:11:27
Message-ID: 40E3B91F.4070606@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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?

I don't really see the point in adding it. If that, why not everything?

Chris

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Pflug 2004-07-01 07:20:05 Re: Adding column comment to information_schema.columns
Previous Message Stergios Zissakis 2004-07-01 06:52:14 Re: ODBC Developers