| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Dave Cramer <Dave(at)micro-automation(dot)net>, Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, 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>, pgsql-hackers(at)postgresql(dot)org, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: Roadmap for FE/BE protocol redesign |
| Date: | 2003-03-13 06:54:24 |
| Message-ID: | 1047538463.3223.27.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera kirjutas K, 12.03.2003 kell 17:10:
> On Wed, Mar 12, 2003 at 03:02:23PM -0000, Dave Page wrote:
>
> > > This may be problematic in the future if we change attrelid, attnum.
> >
> > I suggested using names to Tom for this reason, but he preferred to use
> > attrelid/attnum.
>
> Oh, and what happenned to the attlognum idea? If something that needs
> it is going to be implemented the column should probably be added now
> and used instead of attnum.
I guess that attlognum is _not_ needed here. The only need for attlognum
would be for automatic column ordering when doing "select * " and
"\d table", for all other purposes attnum is much more reliable.
-----------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2003-03-13 07:04:35 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Hannu Krosing | 2003-03-13 06:46:13 | Re: Roadmap for FE/BE protocol redesign |