On lun, 2004-08-09 at 12:41 +0200, Steffen Goeldner wrote: > Olivier Poulet wrote: > [snip] > > > > my $sql =<<'EOFSQL'; > > SELECT > > LOWER(field_one), field_two, UPPER(field_three) > > FROM sample_table (NOLOCK) > > WHERE > > field_one = ? > > EOFSQL [snip] > > Using the MSSQL 'LOWER' and 'UPPER' functions (or any other), gives me > > back 2 "unnamed" columns. > > > > When run through DBD::ADO, $field_one gets clobbered by the contents of > > $field_three, as if $sth->fetch were returning/storing things in a hash. > > I've expanded the statement to fetch several more "unnamed" columns, and > > the value(s) returned, for every "unnamed" column, is _always_ the value > > of the "last" column in the SELECT statement. > > > > However, running the same code/statement with DBD::ODBC does not have > > this behaviour, and the results returned are correct. > > > > Is this a problem, or something known and to avoid when using DBD::ADO ? > > Looks like this bug: > > <http://www.xray.mpe.mpg.de/mailing-lists/dbi/2004-01/msg00206.html>
Yes. That's it. > It was fixed in 2.87: > > <http://www.xray.mpe.mpg.de/mailing-lists/dbi/2004-02/msg00023.html> > > Do you use a pre-2.87 release? ppp query dbd-ado returned "2.90" for som odd reason, when I checked in ADO.pm, I saw "2.84" .... arghh. I removed DBD-ADO and reinstalled 2.91 from ActiveState's repository, and I now get the correct values. Thanks for the help & for the continued improvement to the module, -- Olivier
