Your question doesn't make sense. Text::CSV parses lines (which is weakness of the module), not files.

Maybe what you want is Text::xSV. Consider:

use strict;
use warnings;

use Text::xSV;

my $str = <<FILE;
a,2,"3
a",4,5,6
b,2,3,4,5,6
FILE

open my $inFile, '<', \$str;

my $xsv = Text::xSV->new (fh => $inFile);

$xsv->bind_fields (qw(1 2 3 4 5 6));

while (my @parts = $xsv->get_row ()) {
    s!\n!!g for @parts;
    print "@parts\n";
}

close $inFile;
[download]

Prints:

a 2 3a 4 5 6
b 2 3 4 5 6
[download]

Grandfather,

Strange as it may be, Text::CSV allows you to do

 $colref = $csv->getline ($io);        # Read a line from file $io,
                                       # parse it and return an array
                                       # ref of fields
[download]

It is like an iterator over the file on a line-by-line basis.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

Indeed, that is so with later versions of Text::CSV (although not with earlier versions). But Text::CSV doesn't solve the OP's problem which is that some of the fields straddle lines. Text::xSV handles that case (so long as the field is suitably quoted), Text::CSV does not.

---

Perl's payment curve coincides with its learning curve.

Update: If you want to create a file handle that accesses a scalar, then you can do the following in ≥5.8.0:

open(my $fh, '<', \$blob)
[download]

Getting the data into or out of a database and then connecting this string of data to an IO-handle before giving it to Text::CSV seems complicated.