At Wed, 27 Mar 2002 11:45:10 +0000 (GMT),
Matt Sergeant wrote:
> > Really? I can't see any document like that on sqlite webpage.
>
> Sorry, should have said DBD::SQLite.
I got it.
> > For your information, I compiled sqlite with the default sqlite.h,
> > saying
> >
> > #define SQLITE_ISO8859 1
>
> Right, and DBD::SQLite is compiled with UTF-8 instead, because this is
> Perl, and in Perl characters are unicode code points represented
> internally as UTF-8.
Umm, at least in Japan, many of perl coders handle Japanese characters
in native enodings like EUC-JP (in UNIX) or Shift_JIS (in Win32), even
as characters in Perl internal data.
use bytes;
would be one of the solutions, but I don't think it's the best.
> > We can use famous Jcode module for the conversion, but it'd be very
> > tiresome and thus will reduce this fantasitic sql engine's handiness
> > and portablity. I son't want to see that.
>
> OK, then I suggest that we use a database parameter to turn off SvUTF8on
> calls. Which I believe is what's breaking this.
Seems okay to me, assuming that you mean
DBI->connect('dbi:SQLite:dbname=sqlite.db;utf8=off', '', '');
# or
DBI->connect('dbi:SQLite:dbname=sqlite.db', '', '', { UseUTF8 => 0 });
But I think I should move this discussion onto dbi-jp mailing list
where many Japanese DBI users subbscribe to, and I'll feedback the
result here.
Thanks!
--
Tatsuhiko Miyagawa
