| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: logical column ordering |
| Date: | 2015-03-01 15:12:06 |
| Message-ID: | 20150301151206.GU2384@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby wrote:
> On 2/27/15 2:49 PM, Alvaro Herrera wrote:
> >Tomas Vondra wrote:
> >
> >>1) change the order of columns in "SELECT *"
> >>
> >> - display columns so that related ones grouped together
> >> (irrespectedly whether they were added later, etc.)
>
> FWIW, I find the ordering more important for things like \d than SELECT *.
Logical column ordering is (or should be) used in all places where
column lists are expanded user-visibly. \d would be one of those.
Think column order in the output of a JOIN also, for instance -- they
must follow logical column order.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2015-03-01 15:14:38 | Re: Additional role attributes && superuser review |
| Previous Message | Alvaro Herrera | 2015-03-01 15:09:22 | Re: logical column ordering |