| From: | vinny <vinny(at)xs4all(dot)nl> |
|---|---|
| To: | Sam Mason <sam(at)samason(dot)me(dot)uk> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: R: Field's position in Table |
| Date: | 2009-08-24 19:38:37 |
| Message-ID: | 1251142717.11931.5.camel@vinny-desktop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2009-08-20 at 12:16 +0100, Sam Mason wrote:
> On Thu, Aug 20, 2009 at 11:24:49AM +0200, vinny wrote:
> > I can't really think of any real reason to put the field at a
> > particular position, applications don't reallty care about the order
> > of fields.
>
> Because it's very convenient for ad-hoc queries! PG currently assumes
> that the column order is the same as when it was created but there are
> (unimplemented) suggestions about how to "fix" this. See for example:
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00983.php
>
> --
> Sam http://samason.me.uk/
>
But how is it convenient exactly, is it just a timesaver so you can
SELECT * instead of having to type SELECT firstname, lastname, email?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Rich | 2009-08-24 19:58:58 | Re: R: Field's position in Table |
| Previous Message | Scott Marlowe | 2009-08-24 19:18:22 | Re: How to simulate crashes of PostgreSQL? |