Re: change natural column order - Mailing list pgsql-general

From gnari
Subject Re: change natural column order
Date
Msg-id 014e01c4d746$229d8e50$0100000a@wp2000
Whole thread Raw
In response to Re: change natural column order  ("Dann Corbit" <DCorbit@connx.com>)
List pgsql-general
From: "Dann Corbit" <DCorbit@connx.com>

> From: "Steve Atkins" <steve@blighty.com>
> >
 > > Would you care to expand on why you think this...
> >
> >   my $row = $dbh->selectrow_hashref("select * from $table");
> >   print 'foo = ', $row{'foo'};
> >
> > ...is inherently a a code defect?

> There is an exception to every rule.  If you need a hash for the whole
> row, then you need all the columns.

I think the point was that when the language/libs allow for
easy reading of a row into a hash, it becomes the most
natural and least error prone way. If you add or rename a column,
there are fewer places in the code you need to change.

gnari



pgsql-general by date:

Previous
From: "Dann Corbit"
Date:
Subject: Re: change natural column order
Next
From: Joel
Date:
Subject: Re: USENET vs Mailing Lists Poll ...