From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Justin Clift <jc(at)telstra(dot)net> |
Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Adding column comment to information_schema.columns |
Date: | 2004-07-05 04:38:48 |
Message-ID: | 40E8DB58.8010807@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> One other benefit of having more stuff in information_schema.* is that
> the stuff there is "easier" to look at and figure out what it is. With
> the view definitions that are provided to things like psql and pgAdmin
> when people look at an information_schema view, it provides them a way
> of figuring out where in the internal tables stuff is if they want to
> look for it. i.e. they can find a column in
> information_schema.constraint_column_usage and go "gee where is that in
> the real PostgreSQL tables"? Then look at the code that generates it
> and so on.
OK, so make a pg_columns system view.
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-07-05 04:41:08 | Re: Adding column comment to information_schema.columns |
Previous Message | Justin Clift | 2004-07-05 04:20:27 | Re: Adding column comment to information_schema.columns |