Hello.  I was having some strange problems with fetchall_arrayref in my
code and thought I would share this with the list.  The specific problem
was when I was conducting multiple prepare/execute(s) and then using
fetchall_arrayref to retrieve the data.  The really strange part was it
seemed as if I changed a bit of code here or there my script (I was
currently working on) would work (with multiple statements) but then in
other (seemingly) unrelated scripts all of the statements would not
return data.

Being relatively new to DBI, didn't really think to look there, so I
upgraded mysql to 4.1.11 (from 4.1.5-gamma).  Didn't help.  This was my
current config of DBI and related modules at this time: perl -MDBI -e
'DBI->installed_versions'
  Perl            : 5.008005    (i386-freebsd-64int)
  OS              : freebsd     (5.3-release)
  DBI             : 1.42
  DBD::mysql      : 2.9004
  DBD::Sponge     : 11.10
  DBD::Proxy      : install_driver(Proxy) failed: Can't locate
RPC/PlClient.pm in @INC
  DBD::File       : 0.30
  DBD::ExampleP   : 11.12
  DBD::DBM        : 0.01

I turned tracing on, and on the data that wasn't getting returned to my
script, was showing up just fine in the trace log (the arrayrefs & rows
were all there for the statements I was executing). Decided to upgrade
DBI to 1.48.  Still the same problems.

Decided to upgrade DBD::mysql to 2.9006 and now it seems everything is
working.

perl -MDBI -e 'DBI->installed_versions'
  Perl            : 5.008005    (i386-freebsd-64int)
  OS              : freebsd     (5.3-release)
  DBI             : 1.48
  DBD::mysql      : 2.9006
  DBD::Sponge     : 11.10
  DBD::Proxy      : install_driver(Proxy) failed: Can't locate
RPC/PlClient.pm in @INC
  DBD::File       : 0.33
  DBD::ExampleP   : 11.12
  DBD::DBM        : 0.02

I looked through the changelog for DBD::mysql and didn't find anything
specific to the problem that I was having but maybe there is some
summarization going on in the changelog or I'm not seeing something that
is actual related.

Regards,

Chris


Reply via email to