Re: R: Field's position in Table

From: Yaroslav Tykhiy <yar(at)barnet(dot)com(dot)au>
To: vinny <vinny(at)xs4all(dot)nl>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: R: Field's position in Table
Date: 2009-08-21 01:45:12
Message-ID: 958F6423-708B-486C-BA45-FE8EE7E762A3@barnet.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 20/08/2009, at 7:24 PM, 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.

... unless an application is brain-damaged by its using a wildcard
select, which is a well-known no-no even for home-made scripts, as it
has already been pointed out here. My point here being that
applications' robustness to apparent field order, like liberty,
shouldn't be taken for granted: it needs to be explicitly minded,
protected and sometimes fought for. :-)

Yar

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2009-08-21 01:50:14 Re: R: Field's position in Table
Previous Message Yaroslav Tykhiy 2009-08-21 01:30:06 Re: "Could not open relation XXX: No such file or directory"