Worked like a charm. Thank-you
Glad I could help.
BUT:
Until Tux' change is released on CPAN, please do yourself a favour and add an explaining comment how that trick works. This trick is everything but obvious, and I doubt that it will work for any combination of the relevant modules. Don't make your future self invent a time machine to come back and hurt you for playing dirty tricks.
When the change is released, test it, get rid of my dirty trick, and explicitly require the new version of DBD::CSV.
If your code has to work with "any" version of DBD::CSV, check its version, prefer to use the Tux' official csv_bom attribute, and only if it is not supported, fall back to use the File::BOM trick. Something like this:
use DBD::CSV ();
use if $DBD::CSV::VERSION < 0.50, File::BOM => ();
# ^---- adjust to working version number
my $dbh=DBI->connect(
'dbi:CSV:',
undef,
undef,
{
RaiseError => 1,
PrintError => 0,
f_ext => '.csv',
(
# v---- adjust to working version numbe
+r
$DBD::CSV::VERSION < 0.50
? (f_encoding => 'utf-8):via(File::BOM')
: (csv_bom => 1)
)
}
);
Alternatively, patch DBD::CSV at runtime if it is too old, and use Tux' official attribute csv_bom even with old versions:
#!/usr/bin/perl
use v5.12;
use warnings;
use autodie qw( :all );
use DBI;
use DBD::CSV ();
# v----- adjust to working version
if ($DBD::CSV::VERSION < 0.50) {
require File::BOM;
my $old_connect=\&DBD::CSV::dr::connect;
my $new_connect=sub {
my ($drh, $dbname, $user, $auth, $attr) = @_;
if ($attr && exists($attr->{'csv_bom'}) && $attr->{'cs
+v_bom'}) {
delete $attr->{'csv_bom'};
$attr->{'f_encoding'}='utf-8):via(File::BOM';
}
goto $old_connect;
};
do {
no strict 'refs';
no warnings 'redefine';
*DBD::CSV::dr::connect=$new_connect;
};
}
open my $h,'>:encoding(utf-8)','test.csv';
say $h qq<\x{FEFF}"foo","bar","baz">;
say $h qq<"1","2","3">;
say $h qq<"4","5","6">;
close $h;
my $dbh=DBI->connect(
'dbi:CSV:',
undef,
undef,
{
RaiseError => 1,
PrintError => 0,
f_ext => '.csv',
csv_bom => 1,
}
);
my $sth=$dbh->prepare('select * from test');
$sth->execute();
while (my @a=$sth->fetchrow_array()) {
say join(",",@a);
}
$sth->finish();
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.