Re: CSV EOL Question

[Tux]

The default for the eol attribute is undefined, so the parser can parse records ending on any valid line ending: \r, \r\n, and \n. To produce records, the CSV object should know to do line endings, hence you need to set eol.

It is way to late now to change the default to be sensible and use $/ on print, which would have been a fine choice in the beginning.

As print takes a reference, why not simplify the code and make it faster?:

my $csv = Text::CSV->new ({ binary => 1, auto_diag => 1, eol => $/ });
open my $fh, ">:encoding(utf8)", $filename or die "$filename: $!";

$sth = $dbh->prepare ($query) or # No need to put "'s around $query
    error ($q, "Problem with database call");
if ($sth->execute) { # not using RaiseError?
    while (my $ref = $sth->fetch) { # fetching data by ref is faster
        $csv->print ($fh, $ref);
        }
    }

[jrod16]

Thanks for the insight everyone! Tux, I attempted using your code with the scalar as a reference but the csv command is specifically looking for an array reference. Am I doing something wrong?

if($sth->execute) { while(my $dat = $sth->fetchrow) {$csv->print($fh, 
+$dat);
}

Expected fields to be an array ref at ./name.pl line 65. I feel as though this will only work as \@dat.

[Tux]

Yes, fetchrow returns a list, fetch is an alias to fetchrow_arrayref and returns a reference.