Skip site navigation (1) Skip section navigation (2)

Re: Adding column comment to information_schema.columns

From: Jochem van Dieten <jochemd(at)gmail(dot)com>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adding column comment to information_schema.columns
Date: 2004-07-01 21:08:51
Message-ID: f96a9b8304070114084bbfd1c6@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, 1 Jul 2004 12:23:10 -0500, Bruno Wolff III <bruno(at)wolff(dot)to> wrote:
> 
> Is there any provision in the information schema part of the standard for
> vendor specific extensions?

Yes, there is:

    "An SQL-implementation may define objects that are associated with 
    INFORMATION_SCHEMA that are not defined in this Clause. An
    SQL-implementation or any future version of ISO/IEC 9075 may also
    add columns to tables that are defined in this Clause."
ISO/IEC 9075-11:2003    4.2    Introduction to the Information Schema

If we combine this with the promise that no object defined by the
standard will ever end in an underscore, I can think of no reason not
to add PostgreSQL specific columns as long as they end in an
underscore. The underscore will not only prevent conflicts with future
versions of the standard, it will also serve as a warning that that
column is a PostgreSQL extension.

Jochem

PS I think I spotted an inconsistency in the standard. It says "to
tables that are defined in this Clause", while the Clause only defines
views, not tables.

In response to

Responses

pgsql-hackers by date

Next:From: Dann CorbitDate: 2004-07-01 21:42:02
Subject: Re: demande d'aide
Previous:From: Jeroen T. VermeulenDate: 2004-07-01 21:08:28
Subject: Re: [Re] Re: PREPARE and transactions

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group