Hi. >Which is hardly surprising: YES. Of course.
>> my $hSt =3D $hDb->prepare("SELECT * FROM t1 WHERE NAME like ?");
>> $hSt->execute("%\xB9\xA5%"); #SUKI in KANJI(EUC-JP)
> You are telling MySQL to do the matching. So the matching will use
> whatever character set the database thinks the data uses. If you tell
> the database that the data is ShiftJIS when it is really EUC-JP,
> confusion is to be expected.
I just want to point out what the problem.
-Use appropriate DBMS with character set
-There should be no problem in DBDs
--Regular expressions for matching is in the SQL::Statement (not in
DBD::CSV)
> I could not get any information on mismatching in other character sets
> but do you mean there are no problems with mismatching in DBD::CSV if I
> use UTF8?
I hope so. But other problems might occur. Be careful.
#tu.pl(attached file) seems to work correctly with "no utf8;"
# But with "use utf8;", it will get no lines.
==============================================
KAWAI, Takanori(Hippo2000)
Mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
http://member.nifty.ne.jp/hippo2000/index_e.htm
http://www.hippo2000.info/cgi-bin/KbWikiE/KbWiki.pl
May we translate your pods into Japanese?
-- Japanized Perl Resource Project
http://sourceforge.jp/projects/perldocjp/
==============================================
tu.pl
Description: Binary data
