in reply to accessing data in DBI object

In addition to the comment made by the other monks, I'd like to describe a basic locigical flaw with this code. By using foreach my $row_ref (@$dataOut->fetchrow_array) you are actually iterating over columns, not rows. Changing this to use fetchrow_arrayref only changes it to be a foreach over a list with only one value (doesn't make any sense to do that). What you really meant to use there was fetchall_arrayref. This will return an array of arrays with all the data retrieved by your SQL query.

Update: After reading arturo's response, I'd like to add the following: using while(my @row = $dbh->fetchrow_array) is more memory efficient than using foreach my $row_ref ($dbh->fetchall_arrayref) but fetchall_arrayref may be faster (I'm not sure, it would depend on which DBD module was being used, you'd have to benchmark it). To speak to arturo's recomendation of using fetchrow_hash, it does make the code more maintainable, but less memory efficient, so it really depends on which is more important to you. You can achive the same effect as using fetchrow_hash using fetchall_arrayref by passing an empty hash ref in as an argument to the method.
HTH, Cheers

A truely compassionate attitude towards other does not change, even if they behave negatively or hurt you

—His Holiness, The Dalai Lama

Replies are listed 'Best First'.
Re^2: accessing data in DBI object
by arcnon (Monk) on Apr 14, 2005 at 17:06 UTC
    I was just trying to get at 2 fields and change the data without having to create a new object. Which I did anyway...

    I alway use strict. Yes it throws errors which just told me I wasn't accessing the structure right. But I already knew that. :)

    References eat my lunch anyway. I use objects to dodge them to avoid @{}->[]->{} crap. So when I have to work with them(refs) I am always lost. my solution was as follows 

    $Query_Statement="select fname,lname,address,city,state,zip,phone,emai
+l FROM main order by lname,fname;";

    my $sth = $dbh->prepare($Query_Statement);
    $sth->execute();

    my @array;
    my $dataObjRef = \@array;

    while( my $array_ref = $sth->fetchrow_arrayref){
        #print ">>@$array_ref\n";

        my $fname = $array_ref->[0];
        my $lname = $array_ref->[1];


        my $total += length($fname);
        my $total += length($lname);

        if ((length($fname) + length($lname)) > 18){
            my $Fintial = substr($fname,0,1);
            if ((length($Fintial) + length($lname)) > 18){
                $lname = substr($lname,0,16);
            }
            $array_ref->[0] = $Fintial;
            $array_ref->[1] = $lname;

            #print "$Fintial    $lname\n";
        }
        else{
            next;
        }
        my @newArray = @$array_ref;
        push(@$dataObjRef, \@newArray);
    }

    $sth->finish();
    $dbh->disconnect or warn "Disconnection failed: $DBI::errstr\n";
    return $dataObjRef;
}

    [download]
[reply]
[d/l]

      The only objects you have in this snippet are $dbh (a database handle object) and $sth (a statement handle object). (You called them $DBHandle and $DataOut in the original snippet.) The rest of the variables are just your ordinary garden variety variables: scalars, arrays and hashes. Objects are references (a scalar holding the address of another variable) that have been blessed into a given class. See perldata, perlref, perldsc, perllol, perlobj, perlmod, perltoot and perlboot for the complete details about Perl data types, references, Perl data structures, modules, and objects.

[reply]

In Section Seekers of Perl Wisdom