From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BETWEEN Node & DROP COLUMN |
Date: | 2002-07-04 09:27:18 |
Message-ID: | GNELIHDDFBOCMGBFGEFOGEPHCCAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> BTW there seems a misunderstanding about my posting.
> I'm not objecting to add attisdropped pg_attribute column.
> They are essentially the same and so I used macros
> like COLUMN_IS_DROPPED in my implementation so that
> I can easily change the implementation to use isdropped
> pg_attribute column.
> I'm only correcting the unfair valuation for my
> trial work.
Hiroshi, I totally respect your trial work. In fact, I'm relying on it to
do the attisdropped implementation. I think everyone's beginning to get a
bit cranky here - I think we should all just calm down.
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-07-04 11:59:49 | Re: Scope of constraint names |
Previous Message | Hiroshi Inoue | 2002-07-04 09:21:30 | Re: BETWEEN Node & DROP COLUMN |