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:13:38 |
Message-ID: | 40E8D572.1090205@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> There's a whole lot of difference between the skill level needed to
> query the information_schema and find out things like table and column
> names, vs looking into pg_namespace, pg_class and pg_attribute plus
> understanding the specific info there to work out table and column names.
>
> I reckon that having information "pre-prepared" in views like those in
> information_schema is "of course" going to be easier for people than
> "raw" information our internal catalogs.
>
> Do you get where I'm coming from with this?
Yes, but I disagree. Your opinion is as an experienced user anyway, and
you're just putting words in novice mouths...
We've never had someone complain about querying stuff like that. For
example, why do you need the comments on columns?
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2004-07-05 04:19:38 | Re: Nested Transaction TODO list |
Previous Message | Justin Clift | 2004-07-05 03:58:10 | Re: Adding column comment to information_schema.columns |