From: | Justin Clift <jc(at)telstra(dot)net> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Adding column comment to information_schema.columns |
Date: | 2004-07-05 03:58:10 |
Message-ID: | 40E8D1D2.3000307@telstra.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne wrote:
<snip>
> Anyone who's writing queries that are examing the schema of the database
> is by definition not a newbie...
By newbie here, I mean someone who's a PG "newbie" but has a reasonable
understanding of databases (i.e. Oracle, etc) would generally find the
"information_schema" much easier to locate and use information in
compared to having to learn the PG internals.
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?
Regards and best wishes,
Justin Clift
> Chris
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-07-05 04:13:38 | Re: Adding column comment to information_schema.columns |
Previous Message | Oliver Jowett | 2004-07-05 03:38:13 | Re: Nested Transaction TODO list |