| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN Progress |
| Date: | 2002-07-09 03:49:40 |
| Message-ID: | 838.1026186580@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> That was my first thought also, but then the wrong attnum would be used
>> in the "make_var". Ugh. I think what Chris needs to do is extend the
>> eref data structure so that there can be placeholders for dropped
>> attributes. Perhaps NULLs could be included in the list, and then the
>> code would become like
> Hmmm... I don't get it - at the moment I'm preventing them from even
> getting into the eref and all regression tests pass and every test I try
> works as well...
Are you checking access to columns that're to the right of the one
dropped?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-07-09 04:00:00 | Re: DROP COLUMN Progress |
| Previous Message | Tom Lane | 2002-07-09 03:47:57 | Re: Proposal: CREATE CONVERSION |