Re: forcing utf8 on selected values
- From: alexander@xxxxxxxx (Alexander Foken)
- Date: Wed, 29 Mar 2006 09:23:24 +0200
Soe does a recent version of DBD::Pg (> = 1.40, pg_enable_utf8 database handle attribute), and with my patch (http://www.alexander-foken.de/unicode-patch.txt.gz, http://www.alexander-foken.de/README.unicode-patch.html) also DBD::ODBC 1.13.
For proper Unicode support on Oracle, you should use at least Oracle 9 on both client and server, and you should read http://search.cpan.org/~timb/DBD-Oracle-1.16/Oracle.pm#Unicode at least twice.
Alexander
On 29.03.2006 08:21, Garrett, Philip (MAN-Corporate) wrote:
What database are you using? Perhaps the driver has an option to do this. I know Oracle does.
-----Original Message-----
From: Mark Hedges [mailto:hedges@xxxxxxxx]
Sent: Tue 3/28/2006 9:39 PM
To: dbi-users@xxxxxxxx
Subject: forcing utf8 on selected values
There are several to-do items regarding utf8 that would be great, but aren't here yet.
My database has utf8 columns, server/client character sets and collation. Yet when I call fetchrow, resulting Perl scalars do not have the utf8 flag set. That's really annoying. Am I supposed to call
map { utf8::upgrade($_) } $every,$stupid,$little,$scalar
every time I do a select statement? Or map through the results of any selectall_*ref's? This fixes the display problems when printing a page to a browser with charset utf-8.
Is there an easier way to do this? Please tell me there is.
Mark
--
Alexander Foken
mailto:alexander@xxxxxxxx http://www.foken.de/alexander/
.
- References:
- forcing utf8 on selected values
- From: Mark Hedges
- RE: forcing utf8 on selected values
- From: Philip Garrett
- forcing utf8 on selected values
- Prev by Date: RE: forcing utf8 on selected values
- Next by Date: Re: Message from Maintainer to DBD::mysql users, developers
- Previous by thread: RE: forcing utf8 on selected values
- Next by thread: RE: forcing utf8 on selected values
- Index(es):
Relevant Pages
|