On Thu, Aug 20, 2009 at 7:45 PM, Yaroslav Tykhiy<yar@xxxxxxxxxxxxx> wrote: > 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. :-) And if you're going to write some simplified application that depends on column order, then you should be willing to accept the responsibility of maintain that order. I don't want or need such code in pgsql really, so would rather not have someone playing with the guts in pgsql to make this happen and breaking anything else. And it IS non-trivial to implement in pgsql -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
