| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Rod Taylor" <rbt(at)zort(dot)ca>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Thomas Lockhart" <lockhart(at)fourpalms(dot)org>, "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BETWEEN Node & DROP COLUMN |
| Date: | 2002-07-05 02:07:22 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOCEPJCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > We could change pg_attribute to another name, and create a view called
> > pg_attribute that never returned isdropped columns to the client. That
> > would allow clients to work cleanly, and the server to work cleanly.
>
> Another case where having an informational schema would eliminate the
> whole argument -- as the clients wouldn't need to touch the system
> tables.
Since postgres has so many features that standard SQL doesn't have (eg.
custom operators), how are they going to be shown in the information schema?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-07-05 02:10:37 | Re: BETWEEN Node & DROP COLUMN |
| Previous Message | Tom Lane | 2002-07-05 02:07:19 | Re: BETWEEN Node & DROP COLUMN |