Skip site navigation (1) Skip section navigation (2)

Re: column ordering, was Re: [PATCHES] Enums patch v2

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Gregory Stark <stark(at)enterprisedb(dot)com>
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2
Date: 2006-12-21 17:09:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> Actually, the more I think about it the more I think that 3 numbers
> might be the answer.  99% of the code would use only the permanent ID.
> Display position would be used in *exactly* one place, namely while
> expanding "SELECT foo.*" --- I can't think of any other part of the
> backend that would care about it.

Insert without a column list will need the logical ordering, I think. 
Also use of "like foo" in a create table statement. I'm not dead sure 
there aren't one or two others lurking. But I agree that the number is 



In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-12-21 17:24:18
Subject: Re: pgsql: Initial SQL/XML support: xml data type and initial set of
Previous:From: Matthew T. O'ConnorDate: 2006-12-21 17:03:30
Subject: Re: Autovacuum Improvements

pgsql-patches by date

Next:From: Teodor SigaevDate: 2006-12-21 18:29:30
Subject: Re: [HACKERS] Bundle of patches
Previous:From: Tom LaneDate: 2006-12-21 16:59:47
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group