Fixed it with common sense - using "values %$result" to get back my original struct. Time to upgrade DBI.
Cheers anyway. And a great big nasty insult to the wonderful guy who went and made the selectall_hashref method do what it logically sounds like it should do. ;) fiq On Tue, 2 Apr 2002, Rafiq Ismail (ADMIN) wrote: > Got a slight problem here.. > > Does anyone know why there was at some point a major change in the return > value for DBI::selectall_hashref? And is there a depricated method which > still uses the original prototype? > > My problem: > ----------- > > Using DBI V1.19 on my box, the reported prototype is: > ""selectall_hashref"" > $ary_ref = $dbh->selectall_hashref($statement); > $ary_ref = $dbh->selectall_hashref($statement, \%attr); > $ary_ref = $dbh->selectall_hashref($statement, \%attr, > @bind_values > > > So i wrote shiney happy code and tried it on our production box. > > > On the Production box, using DBI V1.21, the given prototype is: > > selectall_hashref > > $hash_ref = $dbh->selectall_hashref($statement, $key_field); > $hash_ref = $dbh->selectall_hashref($statement, $key_field, > \%attr); > $hash_ref = $dbh->selectall_hashref($statement, $key_field, > \%attr, @bind_values); > > > hmm.. I sware that I saw something similar about a year ago. > > I don't want to go about rewriting code, so has anyone found some secret > undocumented method which still use the original prototype. > > > TIA, > > fiq > > > "__ __ _ __ __ > | \/ | ___ __| | ___ _ __ _ __ | \/ | __ _ _ __ > | |\/| |/ _ \ / _` |/ _ \ '__| '_ \| |\/| |/ _` | '_ \ > | | | | (_) | (_| | __/ | | | | | | | | (_| | | | | > |_| |_|\___/ \__,_|\___|_| |_| |_|_| |_|\__,_|_| |_| > a pathetic example of his organic heritage" > - Bad Religion > > >
