Re: [HACKERS] Re: ORACLE COMMENT statement

Wow, that is nice.

> --- Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Anyway, the \dd command was kind of odd in that it
> > only displayed comments
> > but not what the comments went with.
> >
> > The way I currently have implemented the comments is
> > like this:
> > (Ignoring the actual output format, which is
> > currently under _heavy_
> > development.)
> >
> > peter(at)localhost:5432 play=> \d foobar
> > Table "foobar"
> >
> > Attribute | Type | Info
> > ----------+--------------+---------
> > a | numeric(9,2) | not null
> > b | varchar(5) |
> > c | char(10) |
> > d | char(1) |
> >
> > peter(at)localhost:5432 play=> \set description ""
> > peter(at)localhost:5432 play=> \d foobar
> > Table "foobar"
> >
> > Attribute | Type | Info | Description
> > ----------+--------------+----------+------------
> > a | numeric(9,2) | not null |
> > b | varchar(5) | |
> > c | char(10) | |
> > d | char(1) | |
> >
> > peter(at)localhost:5432 play=> \l
> > List of databases
> >
> > Database | Owner | Encoding |
> > Description
> >
> ----------+----------+----------+---------------------------------------
> > play | postgres | 0 |
> > pwdb | peter | 0 |
> > template1 | postgres | 0 |
> > twig | httpd | 0 | This is for that
> > Twig mailer under PHP
> >
> > (4 rows)
> >
> > peter(at)localhost:5432 play=> \unset description
> > peter(at)localhost:5432 play=> \l
> > List of databases
> >
> > Database | Owner | Encoding
> > ----------+----------+---------
> > play | postgres | 0
> > pwdb | peter | 0
> > template1 | postgres | 0
> > twig | httpd | 0
> >
> > (4 rows)
> >
> > peter(at)localhost:5432 play=> \dd
> > Object descriptions
> >
> > Name | What | Description
> >
> -------------------+----------+------------------------------------------
> > ! | operator | fraction
> > !! | operator | fraction
> > !!= | operator | not in
> > !~ | operator | does not match
> > regex., case-sensitive
> > !~* | operator | does not match
> > regex., case-insensitive
> > !~~ | operator | does not match LIKE
> > expression
> > # | operator | intersection point
> > --<snip>--
> > varcharne | function | not equal
> > varcharoctetlen | function | octet length
> > version | function | PostgreSQL version
> > string
> > width | function | box width
> > xid | type | transaction id
> > xideq | function | equal
> > | | operator | start of interval
> > |/ | operator | square root
> > || | operator | concatenate
> > ||/ | operator | cube root
> > ~ | operator | contains
> > ~ | operator | matches regex.,
> > case-sensitive
> > ~ | operator | path contains point?
> > ~ | operator | polygon contains
> > point?
> > ~* | operator | matches regex.,
> > case-insensitive
> > ~= | operator | same as
> > ~~ | operator | matches LIKE
> > expression
> >
> > (973 rows)
> >
> > peter(at)localhost:5432 play=> \dd version
> > Object descriptions
> >
> > Name | What | Description
> > --------+----------+--------------------------
> > version | function | PostgreSQL version string
> >
> > (1 row)
> >
> >
> > Now if we just put a description on every
> > pre-installed entity (in
> > particular system tables), this is almost like a
> > built-in quick reference!
> >
> > The \dd doesn't do rules yet, I think. But I'll put
> > that in soon.
> >
> > So do you see that as a feasible solution?
> >
> > -Peter
>
> I can't speak for others, but I sure like it.
>
> Mike Mascari
> (mascarim(at)yahoo(dot)com)
>
>
> =====
>
> __________________________________________________
> Do You Yahoo!?
> Bid and sell for free at http://auctions.yahoo.com
>
> ************
>

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