| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Rod Taylor" <rbt(at)zort(dot)ca>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN |
| Date: | 2002-07-16 05:03:14 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOCECMCDAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > In fact, looking at it logically...if all the commands currently are
> > required to check that they're not modifiying a system column,
> then why not
> > add the requirement that they must also not modify dropped
> columns? I can
> > do a careful doc search and try to make sure I've touched everything...
>
> Makes sense. Of course, we could make a syscache that didn't return
> system columns either.
Actually - are you certain that every command uses a SearchSysCache and not
some other weirdness? If we have to do the odd exception, then maybe we
should do them all as 'exceptions'?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-07-16 05:04:24 | Re: DROP COLUMN |
| Previous Message | Christopher Kings-Lynne | 2002-07-16 05:02:14 | Re: DROP COLUMN |