Re^2: DBD::AnyData error message for DBI handle

Shouldn't $sth->{Active} automatically be cleared when $sth->fetch returns undef, thus, when there are no more records to fetch?

And shouldn't clearing $sth->{Active} be the same as calling $sth->finish?

Quoting the DBI docs:

Fetching all the data or calling $sth->finish sets Active off.

Comment on Re^2: DBD::AnyData error message for DBI handle Select or Download Code

Replies are listed 'Best First'.
Re^3: DBD::AnyData error message for DBI handle by jZed (Prior) on Jun 13, 2005 at 18:03 UTC
Yes, that's the way it should work. However the old DBD::File got it wrong. Newer versions of DBD::File corrected it, and I just haven't released a newer DBD::AnyData to follow suit. In normal practice, one should never explicitly set $sth->{Active}, I'm only recommending it in this case as a temporary work around to shut off the annoying (but harmless) warning about Active handles in DESTROY. Alternate solutions would be to go back to an earlier DBD::FIle or to patch DBD::AnyData to remove the finish() and DESTROY() methods of ::st.	[reply]

Replies are listed 'Best First'.

Re^3: DBD::AnyData error message for DBI handle
by jZed (Prior) on Jun 13, 2005 at 18:03 UTC

Yes, that's the way it should work. However the old DBD::File got it wrong. Newer versions of DBD::File corrected it, and I just haven't released a newer DBD::AnyData to follow suit. In normal practice, one should never explicitly set $sth->{Active}, I'm only recommending it in this case as a temporary work around to shut off the annoying (but harmless) warning about Active handles in DESTROY. Alternate solutions would be to go back to an earlier DBD::FIle or to patch DBD::AnyData to remove the finish() and DESTROY() methods of ::st.

[reply]