in reply to Using Data::Dumper on a MySQL statement handle

What part of this has you stumped?

Please show the output of print Dumper($sth) (which should have a terminal semicolon, by the way) and identify what aspect of this you are having difficulty with.

-- Ken

Replies are listed 'Best First'.
Re^2: Using Data::Dumper on a MySQL statement handle
by Anonymous Monk on Nov 10, 2010 at 17:18 UTC
    Ooops, that would be much more helpful. Here's the Dumper output. 
    $VAR1 = bless( {}, 'DBI::st' );

    [download]
[reply]
[d/l]

      This sounds like a follow-up to Perl DBI: Overloading statement handle. If so, can you post the code that you finally came up with. Actually, even if it's something completely different, still post the code.

      Also, can you run print Dumper($dbh);, and post that output too.

      -- Ken

[reply]
[d/l]
        I did have a similar problem that was very much like this. Using Dumper against $sth/$dbh is normally futile because the data is hidden behind a tie(). In cases of subclassing Perl's DBI, you'll laugh, you'll cry, and you may want to consider callbacks instead.
        http://search.cpan.org/~timb/DBI/DBI.pm#Callbacks
        Ken, I'll go back to the Perl DBI question I had previously and post what worked for me.
[reply]
        Thanks for that link. print Dumper($dbh) has almost the same result. 
        $VAR1 = bless( {}, 'DBConnect::db' );

        [download]
        I am starting to think that Dumper just won't work on DBI.
[reply]
[d/l]

In Section Seekers of Perl Wisdom