> From: Jeff Zucker <[EMAIL PROTECTED]>
> Date: 2004/07/09 Fri PM 04:18:15 GMT
> What happened when you tried? If it didn't work as expected, what
> happened instead?
I'm capturing and printing the number of rows selected with
print "Loading data from $datafile into table $tablemap...\n";
my $Text_dbh = DBI->connect("DBI:CSV:f_dir=$arg_data_location");
$Text_dbh->{'csv_tables'}->{$tablemap} = {
'eol' => "\n",
'sep_char' => "\|",
'quote_char' => "\"",
'escape_char' => "\"",
'file' => "$datafile",
'col_names' => [EMAIL PROTECTED]
};
my $Text_sth = $Text_dbh->prepare("SELECT * FROM $tablemap");
my $row_count = $Text_sth->execute() || die "Could not get the data...\n";
print "$row_count rows in $tablemap!\n";
And on the Unicode files it prints:
Loading data from consum.dat into table CONSUM...
0E0 rows in CONSUM!
Done!
> If you look at the archives of this mailing list, you'll find a whole
> discussion of using DBD::CSV with Unicode in the past month including
> reports of people in Japan who have it working fine. (search for
> "MultiByte Character Sets and False Matches" and read the whole thread,
> especially the last couple of posts)
I will go digging through them...
> BTW, how did your issue "Re: perl DBD::CSV and non-printing ASCII" turn
> out? I think the test script I wrote conclusively proved the issue
> wasn't with DBD::CSV, was that your conclusion also?
Yes, you were indeed correct; I apologize for not getting back to you on it.
The issue had nothing to do with DBD::CSV and everything to do with how I has
handling the data... :-(
> Jeff
Thank you,
amonotod
--
`\|||/ amonotod@ | subject line:
(@@) charter.net | no perl, no read...
ooO_(_)_Ooo________________________________
_____|_____|_____|_____|_____|_____|_____|_____|
