DBIx::Class Looping thru resultset

[phildeman]

Hi All,

Can variables be used in place of column names when looping through DBIx::Class array of objects.
For example:

my @db_colnames = ('lastname','firstname','middlename');

my @rows = $schema->resultset( 'myTable' )->search({},
                                                      {order_by => [qw
+/ lastname firstname middlename /] }
);

foreach my $row (@rows) {
    foreach my $col (@db_colnames) {
       print $row->$col ."\t";
    }
    print "\n";
}

No value printed. However, when I used the actual column name to retrieve the data, it worked fine. For example:

.
.
print $row->lastname . "\t" . $row->firstname . "\t" . $row->middlenam
+e . "\t";
print "\n";
.
.

Thanks for your help.

[Your Mother]

That definitely works; method name as $scalar. Not sure where it's falling down for you. As someone allergic to any kind of string concatenation, implied or literal, might I suggest something more like this–

my @db_colnames = qw( lastname firstname middlename );

my $rs = $schema
    ->resultset('myTable')
    ->search({},
             { order_by => \@db_colnames });

for my $row ( $rs->all ) {
    my %data = $row->get_columns;
    print join("\t", @data{@db_colnames}), "\n";
}

[Myrddin Wyllt]

If you just want the data in the column, rather than any inflated object DBIC has associated with it (DateTime, foreign key Row objects etc.), it's probably best to use $row->get_column($col), which avoids the variable / method name substitution.

Having said that, I've just tried your code with one of my own databases and it works fine. If there was a problem with the column names, I would expect DBIx to complain, so it's possibly a typo somewhere else.

[Ovid]

As has been pointed out, that syntax is legal. Have you verified that @rows actually has data?