go ahead... be a heretic | |
PerlMonks |
DBD: bind_column behviour with multiple "unnamed" columnsby olivierp (Hermit) |
on Aug 06, 2004 at 12:00 UTC ( [id://380503]=perlquestion: print w/replies, xml ) | Need Help?? |
olivierp has asked for the wisdom of the Perl Monks concerning the following question:
Fellow monks I have the following snippet running on Win32, against a MSSQL2000 server: When this runs, $field_one gets clobbered by the contents of $field_three, as if $sth->fetchwere returning a hash, but it's documented as being an alias of $sth->fetchrow_arrayref Doing a print join "<->", @{$sth->{NAME}}; gives <->field_two<->, "confirming" my idea. I have changed my query to explicitly name the columns, but am curious to understand what's going on. Update: gmax has spotted where the problem is. The behaviour I see is using DBD::ADO with a sqloledb Provider When using DBD::ODBC, "unnamed" colums retain their values and do not step over each other. Update 2: As per DBD:ADO maintainer, this is a bug in versions <2.87. I was using 2.84, and after an update to version 2.91, my "unnamed" columns work correctly. -- Olivier
Back to
Seekers of Perl Wisdom
|
|