| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Justin Clift <jc(at)telstra(dot)net>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding column comment to information_schema.columns |
| Date: | 2004-07-03 14:06:48 |
| Message-ID: | 20040703140648.GA21258@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jul 03, 2004 at 18:02:01 +0800,
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
> >>Why are they useful???? If you want PG specific stuff then use the PG
> >>specific catalogs!!!
> >
> >The information schema could be used to provide a more stable interface.
> >The pg catalog changes from release to release and it would be nice to
> >be able to write code which is more future proof.
>
> Really? It will have the same problem! That being that when we change
> stuff in the catalogs, we will need to change it in the info schema as
> well more than likely...
That isn't my expectation. I would expect that in most cases the pg catalog
would be changed to include more information, not less and that the
old information affected by a change could still be obtained by using
a more complicated view.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-07-03 14:25:20 | Re: Nested Transactions, Abort All |
| Previous Message | Christopher Kings-Lynne | 2004-07-03 11:12:02 | Re: working on support triggers on columns |