From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | Karl DeBisschop <kdebisschop(at)range(dot)infoplease(dot)com> |
Cc: | PostgreSQL-general <pgsql-general(at)postgreSQL(dot)org> |
Subject: | Re: pg_description |
Date: | 2000-06-13 16:53:56 |
Message-ID: | 39466724.260B6BCF@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-general |
Karl DeBisschop wrote:
>
> I'm hoping to use the pg_description table (in 7.0.2) to make a few
> databases
> more decipherable to local developers.
>
> Unfortunately, the only way I can see to put data in is by directly
> updating
> the pg_description table. Is there any documenation for possible
> alternative
> procedures? I was unfortunately unable to find any.
>
> What I would like would be something like:
>
> ALTER TABLE foo (ADD|UPDATE) DESCRIPTION 'Some Text Here';
>
> and of course the ability set change psql setting to display
> descriptions for
> tables when I do '\dt'
>
> Does anything like this exist? Is it planned?
To add descriptions:
COMMENT ON TABLE foo IS 'Some Text Here';
To drop the descriptions:
COMMENT ON TABLE foo IS NULL;
\h COMMENT should give yo all the details. Naturally, the
comments are dropped when the associated object is dropped. You
can comment on any PostgreSQL object and the comments are dumped
with pg_dump.
Hope that helps,
Mike Mascari
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Elphick | 2000-06-14 20:22:47 | postgresql 7.0.2-1 Debian package now available |
Previous Message | Karl DeBisschop | 2000-06-13 16:14:49 | pg_description |
From | Date | Subject | |
---|---|---|---|
Next Message | Haroldo Stenger | 2000-06-13 17:06:42 | Revisited: Does error within transaction imply restarting it? |
Previous Message | Karl DeBisschop | 2000-06-13 16:14:49 | pg_description |