Re: ORACLE COMMENT statement

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Mike Mascari <mascarim(at)yahoo(dot)com>
Cc: peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: ORACLE COMMENT statement
Date: 1999-10-15 01:54:16
Message-ID: 199910150154.VAA11206@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Hello Bruce,
>
> I've just submitted a patch to the patches list which
> implements Oracle's COMMENT statement. It will
> insert/update/delete the appropriate OID for the
> table or column targeted for the comment. It should
> apply cleanly against current. If it passes your
> scrutiny, I was wondering a couple of things:
>
> 1. Might it be possible for psql
> (a.k.a Peter Eisentraut) to display the comments
> associated with tables, views, and columns in
> its \d output? Or perhaps another \ command?

Sure. \dd does that already.

>
> 2. Should I write up SGML for it (as well as for
> TRUNCATE TABLE)?

I did that for Truncate. You can see it in the docs. If you want to
write on on this, that would be good. It seems more complex.

>
> 3. Should I expand it beyond ORACLE's syntax to
> include functions, types, triggers, rules, etc.?

Sure, why not. \dd already handles it.

>
> On the TODO list its listed as:
>
> Allow pg_descriptions when creating types, tables,
> columns, and functions

Yep. Removed the 'table' entry, and marked it as done.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-10-15 02:37:03 Why I am writing a book
Previous Message Clark C. Evans 1999-10-15 01:48:58 Re: [INTERFACES] pgbash-1.1.1 release