| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "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-04 07:07:59 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOMEPFCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > No, he only breaks even for client cleanliness --- either approach
> > *will* require changes in clients that look at pg_attribute.
>
> Uh, Christopher already indicated three clients, psql, pg_dump, and
> another that will not require changes for Hiroshi's approach, but will
> require changes for isdropped. That doesn't seem "break even" to me.
And Tom pointed out that I was wrong...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2002-07-04 09:18:02 | Re: BETWEEN Node & DROP COLUMN |
| Previous Message | Christopher Kings-Lynne | 2002-07-04 06:54:14 | Re: BETWEEN Node & DROP COLUMN |